Date: Tue, 10 Sep 2013 12:23:31 +0100 From: krad <kraduk@gmail.com> To: J David <j.david.lists@gmail.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) Message-ID: <CALfReydJkRCXE_pVMicNZTdb6E5JY%2B=yRieZtT2REXoN8s5cqA@mail.gmail.com> In-Reply-To: <CALfReycWB=-uQppiHkmJ0WuQkKZ60--zDzWUAFzXxKZse9HxTw@mail.gmail.com> References: <CABXB=RTz6jM=B895Bo6Kp-ZAf2pvTZkm-HfS=PrfX=aMKqjMbw@mail.gmail.com> <522D67DB.7060404@infracaninophile.co.uk> <CALfReyeAnpDAZEYPNP4-OZy3wCc9Yt1nurhfgA%2B=o7WFVZGHLA@mail.gmail.com> <CABXB=RQ_D2nwDYJf48dkM%2BQZbF565snvowe2cdG=0m6LKW831w@mail.gmail.com> <522E07B1.5030205@platinum.linux.pl> <CABXB=RQ9ty66OpA_HCHoKvvPbHMpBRGUyOFDxG8_9P7WWy8t_w@mail.gmail.com> <CALfReycWB=-uQppiHkmJ0WuQkKZ60--zDzWUAFzXxKZse9HxTw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
you could probably play with the canmount property though On 10 September 2013 12:22, krad <kraduk@gmail.com> wrote: > "Using mountpoint=legacy seems a little conceptually challenged, > especially given that the description of a legacy mount is:" > > not really as what is one of the 1st things the kernel does after it is > loaded with all its modules? It looks to mount the root filesystem. This is > something that happens outside zfs's control from what I understand so is a > legacy mount rather than a zfs controlled one. The bootfs property of a > pool is actually used by the zfsloader to locate the file system the > loader.conf etc is on. The loader may or may not choose to pass this > parameter through to the kernels environment, and its totally possible to > have / set to a different dataset than the bootfs option. > > "How does mountpoint=legacy interact with importing the pool on another system, > or from a LiveCD, with " -o altroot=/mnt " ? (A case where > mountpoint=/ works perfectly.)" > > Its doesn't get mounted as its legacy, ie you have to mount the dataset > manually where ever you see fit > > "And, finally, what would have to change to support a ZFS root filesystem > set as mountpoint=/ instead of mountpoint=legacy ?" > > Why would you want to? > > > > > On 9 September 2013 19:46, J David <j.david.lists@gmail.com> wrote: > >> On Mon, Sep 9, 2013 at 1:38 PM, Adam Nowacki <nowakpl@platinum.linux.pl> >> wrote: >> > zfs set mountpoint=legacy data/root >> > together with >> > zpool set bootfs=data/root data >> >> This does appear to work, thanks. So the key steps seem to be: >> >> 1) zfs_load="YES" in loader.conf >> 2) zfs_enable="YES" in rc.conf >> 3) Set bootfs=data/root in the zpool. >> 4) Set mountpoint=legacy on the root fs >> >> Using mountpoint=legacy seems a little conceptually challenged, >> especially given that the description of a legacy mount is: >> >> "If a file system's mount point is set to legacy, ZFS makes no attempt >> to manage the file system, and the administrator is responsible for >> mounting and unmounting the file system." >> >> Is this bending things to claim setting bootfs is adequate example of >> the administrator's responsibility to mount the file system? (Even >> though that is clearly also part of ZFS.) >> >> How does mountpoint=legacy interact with importing the pool on another >> system, or from a LiveCD, with " -o altroot=/mnt " ? (A case where >> mountpoint=/ works perfectly.) >> >> And, finally, what would have to change to support a ZFS root >> filesystem set as mountpoint=/ instead of mountpoint=legacy ? >> >> Thanks! >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReydJkRCXE_pVMicNZTdb6E5JY%2B=yRieZtT2REXoN8s5cqA>