Date: Thu, 14 Aug 1997 00:11:03 -0700 From: David Greenman <dg@root.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: "Wayne M. Barnes" <wayne@barnes1.wustl.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: NFS ignores mount point. It's happening again. Message-ID: <199708140711.AAA24832@implode.root.com> In-Reply-To: Your message of "Wed, 13 Aug 1997 23:36:03 PDT." <Pine.BSF.3.96.970813232910.2059H-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Sun, 10 Aug 1997, Wayne M. Barnes wrote: > >> Dear FreeBSDers, >> >> mount newcomputer:/ /newcomputer >> (cd /usr; tar cf - .)|(cd /newcomputer/usr; tar xvf -) >> >> df on new computer shows / filling up, and /usr not changing >> at all. The NFS mount is ignoring and disrespecting the mount points >> on newcomputer. The tar copy is filling up /, ***under the /usr mount point*** >> >> Is this misbehaviour, or what? Is this a bug in mount, NFS, tar, or me? > >I wasn't aware nfs mounts crossed mountpoints. If you want to do this, >don't you have to specify -alldirs in /etc/exports and mount the >sub-mountpoints manually? Am I barking up the wrong file tree? :-) -alldirs only allows a client machine to mount any directory under the server's mountpoint; it doesn't have any affect on traversing a (server) mount point. Basically, what he's doing above isn't complete. He needs to have "mount newcomputer:/usr /newcomputer/usr", as well as any other filesystems that are mounted on newcomputer's /. NFS has always been like this and I think the reason has to do with how file handles are generated. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708140711.AAA24832>