1. sorry for the delay in replying.
2. the reason that I was originally using zfs destroy was that beadm destroy
failed.
3. Current state of affairs:
~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
b101b - - 6.14G static 2008-11-14 09:17
b103pre NR / 16777216.03T static 2008-12-07 11:25
b103pre-2 - - 6.65M static 2008-12-08 13:22
~# beadm create test
~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
b101b - - 6.14G static 2008-11-14 09:17
b103pre NR / 16777216.03T static 2008-12-07 11:25
b103pre-2 - - 6.65M static 2008-12-08 13:22
test - - 112.0K static 2008-12-18 09:59
~# beadm activate test
Unable to activate test.
Unknown external error.
~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
b101b - - 6.14G static 2008-11-14 09:17
b103pre NR / 16777216.03T static 2008-12-07 11:25
b103pre-2 - - 6.65M static 2008-12-08 13:22
test - - 250.0K static 2008-12-18 09:59
~# beadm destroy test
Are you sure you want to destroy test? This action cannot be undone(y/[n]): y
~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
b101b - - 6.14G static 2008-11-14 09:17
b103pre NR / 16777216.03T static 2008-12-07 11:25
b103pre-2 - - 6.65M static 2008-12-08 13:22
Notice: A. the incorrect size for the current BE, follows the active BE around
like a faithful dog.
B. if I zfs set mountpoint=, mount, unmount re-set mountpoint=, then beadm
activate can usually be made to work. this is one reason I wanted to lighten
the BE load cause even with a script to do the work, Im pretty tired of it,
every update.
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
