Michael Schuster wrote: > 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 >
Yes, that command should have worked. You could be running into an issue where sometimes snapshotting a dataset fails because of 6462803, and so we fail to create the clone BE. Next time this happens, try mounting then unmounting the BE, then clone it. (The "Mount busy" error returned is a bug. libbe is assuming all EBUSY errors are "mount busy". I'll file a bug on this.) > > 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? If what you ran into was indeed the above, then by booting -105, any unplayed logs would have been played, and so then snapshotting and cloning no longer fails. -ethan
