I forgot to add that the ABE are reflected in your rpool which is one
reason it is recommended to let rpool have the complete disk. The
ABEs just store the new bits compared to the BE that was active when
you did the update. There is a hierarchy but it is not much of an
issue. The beadm destroy manages the merging and the size will change
to suit. I have had 6 or 7 earlier BE's which have been destroyed with
no problems. motie:/home/lw31248 ->zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 36.0G 111G 76.5K /rpool rpool/ROOT 14.3G 111G 18K legacy rpool/ROOT/opensolaris-129 3.59G 111G 9.40G /mnt rpool/ROOT/opensolaris-sru5 14.7M 111G 7.04G / rpool/ROOT/opensolaris-sru6 20.6M 111G 7.07G / rpool/ROOT/opensolaris-sru7 10.7G 111G 8.25G / rpool/ROOT/opensolaris-sru7-ABE 77K 111G 7.07G / rpool/dump 1023M 111G 1023M - rpool/export 19.6G 111G 23K /export rpool/export/home 16.3G 111G 21K /export/home rpool/export/home/lw31248 16.3G 111G 3.36G /export/home/lw31248 rpool/export/install 2.57G 111G 2.57G /export/install rpool/export/opt 725M 111G 188M /export/opt rpool/swap 1023M 111G 842M - ...Les Leslie H Wood wrote, On 01/07/10 16:51: ABE's are managed by the beadm command which is pretty simple. |
_______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org