Looking for a way to mount a zfs filesystem ontop of another zfs filesystem without resorting to legacy mode. This message posted from opensolaris.org
Mike DeMarco wrote:> Looking for a way to mount a zfs filesystem ontop of another zfs > filesystem without resorting to legacy mode.doesn''t simply ''zfs set mountpoint=...'' work for you? -- Michael Schuster Recursion, n.: see ''Recursion''
> Mike DeMarco wrote: > > Looking for a way to mount a zfs filesystem ontop > of another zfs > > filesystem without resorting to legacy mode. > > doesn''t simply ''zfs set mountpoint=...'' work for you? > > -- > Michael Schuster > Recursion, n.: see ''Recursion'' > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discu > sswell if you create let say a local/apps and a local/apps-bin then zfs set mountpoint=/apps local/apps zfs set mountpoint=/apps/bin local/apps-bin now if you reboot the system there is no mechanism to tell zfs to mount /apps first and /apps/bin second so you could get /apps/bin mounted first and then /apps either will mount overtop or wont mount. This message posted from opensolaris.org
On Mon, Oct 22, 2007 at 11:41:57AM -0700, Michael Schuster wrote:> Mike DeMarco wrote: > > Looking for a way to mount a zfs filesystem ontop of another zfs > > filesystem without resorting to legacy mode. > > doesn''t simply ''zfs set mountpoint=...'' work for you?Does this have boot-time problems? I don''t see how to force an ordering of pool imports. -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
On Mon, Oct 22, 2007 at 12:16:21PM -0700, Mike DeMarco wrote:> > Mike DeMarco wrote: > > > Looking for a way to mount a zfs filesystem ontop > > of another zfs > > > filesystem without resorting to legacy mode. > > > > doesn''t simply ''zfs set mountpoint=...'' work for you? > > > > -- > > Michael Schuster > > Recursion, n.: see ''Recursion'' > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discu > > ss > > well if you create let say a local/apps and a local/apps-bin then > zfs set mountpoint=/apps local/apps > zfs set mountpoint=/apps/bin local/apps-bin > > now if you reboot the system there is no mechanism to tell zfs to > mount /apps first and /apps/bin second so you could get /apps/bin > mounted first and then /apps either will mount overtop or wont mount.The datasets should be mounted in lexical mountpoint order so that shorter mountpoints are mounted first (see dataset_cmp() in zfs_main.c). Are you seeing different behavior? - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
No boot problems. The zfs filesystems are in the same pool. What would be nice is something like zfs set mountorder=1 local/apps zfs set mountorder=2 local/apps-bin or something along that line. So one zfs filesystem can be reliably mounted to a point inside another zfs filesystem. This message posted from opensolaris.org
M D wrote:> No boot problems. The zfs filesystems are in the same pool. What would > be nice is something like> zfs set mountorder=1 local/apps > zfs set mountorder=2 local/apps-bin> > or something along that line. So one zfs filesystem can be reliably > mounted to a point inside another zfs filesystem.I may be a missing the obvious here: what are you trying to solve that Eric''s explanation didn''t cover? Michael -- Michael Schuster Recursion, n.: see ''Recursion''