Date: Fri, 17 Jun 2011 23:54:24 -0400 From: Lars Kellogg-Stedman <lars@seas.harvard.edu> To: Christian Degen <bubulein@freenas.org> Cc: freebsd-jail@freebsd.org Subject: Re: Exposing a hierarchy of ZFS datasets inside multiple jails Message-ID: <BANLkTi=jC-st4ka-k4De0BR5fawPKxo8AA@mail.gmail.com> In-Reply-To: <4DFBBD17.6000604@freenas.org> References: <BANLkTikrWYnBAnQsXZ535OdX5tVp9eOrNQ@mail.gmail.com> <4DFBBD17.6000604@freenas.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Why dont you create a NFS-loopback? You can create a fstab for each jail = and > use this to mount the nfs-shares. > from rc.conf > jail_alcatraz_fstab=3D"/mnt/tank/freebsd/fstab.alcatraz" > > fstab.alcatraz > 127.0.0.1:/foo/bar =A0 =A0/var/jails/alcatraz/mnt/bar =A0 =A0nfs =A0 =A0r= w =A0 =A00 =A0 =A00 The problem with this solution -- if I understand you correctly -- is that it doesn't deal well with a population of home directories that may change while the jail is running. This is what I described as "writing a poorly designed automounter". I could... - Iterate over /home - Generate an appropriate /etc/fstab.<jail> entry for each directory - Start the jail ...but the only way to pick up changes would be to reboot the jail. This is certainly a functional fallback position, but I'd love a more graceful solution. --=20 Lars Kellogg-Stedman <lars@seas.harvard.edu> Senior Technologist Harvard University SEAS Academic and Research Computing (ARC)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=jC-st4ka-k4De0BR5fawPKxo8AA>