On Wed, May 10, 2006 at 02:07:01AM -0600, Lori Alt wrote:
> 5. The new BE works fine, so the administrator decides to promote
> the BE's dataset (which is still a clone) to primary dataset status.
> Here I'm not sure what's best: should liveupgrade promote the
> dataset as part of its management of boot environments? Or
> should the administrator have to (or be able to) promote a
> a bootable dataset explicitly? I'll have to give that one a bit of
> thought, but one way or another, this happens:
>
> # zfs promote pool/root_sol10_u5
But, does it matter? I mean, unless you want to release space
associated with old BEs that you never use anymore, it probably doesn't
matter much.
More importantly, from the user perspective, is re-arranging the GRUB
menu so the BEs appear in the user's preferred order and setting a
proper default.
> 6. So we can rename the newly-promoted BE if we want, but let's
> assume we leave it with its name "root_sol10_u5". Now if we
> want to get rid of the old U4 root dataset, we should do the
> following:
>
> # ludelete root_sol10_u4
>
> which, in addition to the usual liveupgrade tasks to delete the
> BE, will do this:
>
> # zfs destroy pool/root_sol10_u4
This would require promotion, yes, and answers the above question about
whether the sysadmin should have to manually promote BEs ("no").
One possibility would be to always promote, at boot time, whichever BE
is being booted, unless promotion is expensive.
Could there be a tree of BEs? Does this make any difference?
Nico
--
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
