NAME USED AVAIL REFER MOUNTPOINT pool/ROOT 5.58G 53.4G 18K legacy What''s the legacy mount for? Is it related to zones? thanks, -- Alan Burlison --
Alan Burlison wrote:> NAME USED AVAIL REFER MOUNTPOINT > pool/ROOT 5.58G 53.4G 18K legacy > > What''s the legacy mount for? Is it related to zones? > > >Basically, it means that we don''t want it mounted at all because it''s a placeholder dataset. It''s just a container for all the boot environments on the system. Though, now that I think about it, we should have made it "none". Lori
Lori Alt wrote:> Basically, it means that we don''t want it mounted at all > because it''s a placeholder dataset. It''s just a container for > all the boot environments on the system. > Though, now that I think about it, we should have > made it "none".Ok, thanks for the explanation :-) -- Alan Burlison --
Lori Alt wrote:> Alan Burlison wrote: >> NAME USED AVAIL REFER MOUNTPOINT >> pool/ROOT 5.58G 53.4G 18K legacy >> >> What''s the legacy mount for? Is it related to zones? >> >> >> > Basically, it means that we don''t want it mounted at all > because it''s a placeholder dataset. It''s just a container for > all the boot environments on the system. > Though, now that I think about it, we should have > made it "none".Why none as the mountpoint rather than canmount=off ? -- Darren J Moffat
Darren J Moffat wrote:>Lori Alt wrote: > > >>Alan Burlison wrote: >> >> >>>NAME USED AVAIL REFER MOUNTPOINT >>>pool/ROOT 5.58G 53.4G 18K legacy >>> >>>What''s the legacy mount for? Is it related to zones? >>> >>> >>> >>> >>> >>Basically, it means that we don''t want it mounted at all >>because it''s a placeholder dataset. It''s just a container for >>all the boot environments on the system. >>Though, now that I think about it, we should have >>made it "none". >> >> > >Why none as the mountpoint rather than canmount=off ? >canmount=off would have been a good option too. I still would have wanted to set the mount point to either legacy or none since a real mountpoint would have been meaningless and would have still been inheritable. Lori -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080804/a4fb6b74/attachment.html>
Michael Schuster
2008-Aug-04 16:14 UTC
[zfs-discuss] ''legacy'' mount after installing B95
Lori Alt wrote:> > > Darren J Moffat wrote: >> Lori Alt wrote: >> >>> Alan Burlison wrote: >>> >>>> NAME USED AVAIL REFER MOUNTPOINT >>>> pool/ROOT 5.58G 53.4G 18K legacy >>>> >>>> What''s the legacy mount for? Is it related to zones? >>>> >>>> >>>> >>>> >>> Basically, it means that we don''t want it mounted at all >>> because it''s a placeholder dataset. It''s just a container for >>> all the boot environments on the system. >>> Though, now that I think about it, we should have >>> made it "none". >>> >> >> Why none as the mountpoint rather than canmount=off ? > > canmount=off would have been a good option too. I still would > have wanted to set the mount point to either legacy or none since > a real mountpoint would have been meaningless and would > have still been inheritable.I personally find ''legacy'' a little misleading, and - if possible - would suggest changing that to ''none'' Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see ''Recursion''
Michael Schuster wrote:> Lori Alt wrote: > >> Darren J Moffat wrote: >> >>> Lori Alt wrote: >>> >>> >>>> Alan Burlison wrote: >>>> >>>> >>>>> NAME USED AVAIL REFER MOUNTPOINT >>>>> pool/ROOT 5.58G 53.4G 18K legacy >>>>> >>>>> What''s the legacy mount for? Is it related to zones? >>>>> >>>>> >>>>> >>>>> >>>>> >>>> Basically, it means that we don''t want it mounted at all >>>> because it''s a placeholder dataset. It''s just a container for >>>> all the boot environments on the system. >>>> Though, now that I think about it, we should have >>>> made it "none". >>>> >>>> >>> Why none as the mountpoint rather than canmount=off ? >>> >> canmount=off would have been a good option too. I still would >> have wanted to set the mount point to either legacy or none since >> a real mountpoint would have been meaningless and would >> have still been inheritable. >> > > I personally find ''legacy'' a little misleading, and - if possible - would > suggest changing that to ''none'' > > >I agree. I just filed 6733316 and will try to include this in my next bug fix delivery. Lori -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080804/9efc06c3/attachment.html>