Kyle McDonald wrote: > Tim Haley wrote: >> Ross wrote: >> >>> While it's good that this is at least possible, that looks horribly >>> complicated to me. >>> Does anybody know if there's any work being done on making it easy to >>> remove obsolete >>> boot environments? >>> >> If the clones were promoted at the time of their creation the BEs would >> stay independent and individually deletable. Promotes can fail, though, >> if there is not enough space. >> >> I was told a little while back when I ran into this myself on an Nevada >> build where ludelete failed, that beadm *did* promote clones. This >> thread appears to be evidence to the contrary. I think it's a bug, we >> should either promote immediately on creation, or perhaps beadm destroy >> could do the promotion behind the covers. >> > If I understand this right, the latter option looks better to me. Why > consume the disk space before you have to? > What does LU do? >
ludelete doesn't handle this any better than beadm destroy does, it fails for the same reasons. lucreate does not promote the clone it creates when a new BE is spawned, either. -tim > -Kyle > >> -tim >> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
