all,
while experimenting with beadm, I see this behaviour:
$ beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
osol-101 - - 3.37G static 2008-11-07 16:08
osol-102 NR / 18.90G static 2008-11-22 22:01
osol-105 - - 1.31G static 2009-01-15 08:25
osol-96 - - 127.63M static 2008-10-31 23:07
$ pfexec beadm create -e osol-105 osol-105a
Unable to create osol-105a.
Mount busy.
$ pfexec beadm create osol-102 at now
$
the way I read the man-page, the first "beadm create" should have worked:
beadm create [-a] [-d description]
[-e non-activeBeName | beName at snapshot]
[-o property=value] ... [-p zpool] beName
I then rebooted into -105, and tried again:
$ beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
osol-101 - - 3.37G static 2008-11-07 16:08
osol-102 R - 18.90G static 2008-11-22 22:01
osol-105 N / 1.31G static 2009-01-15 08:25
osol-96 - - 127.63M static 2008-10-31 23:07
$ pfexec beadm create osol-105a
$
what am I missing?
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
