From owner-freebsd-questions  Thu Aug 14 00:09:15 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA00633
          for questions-outgoing; Thu, 14 Aug 1997 00:09:15 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA00613
          for <freebsd-questions@FreeBSD.ORG>; Thu, 14 Aug 1997 00:09:09 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA24832;
	Thu, 14 Aug 1997 00:11:03 -0700 (PDT)
Message-Id: <199708140711.AAA24832@implode.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. 
In-reply-to: Your message of "Wed, 13 Aug 1997 23:36:03 PDT."
             <Pine.BSF.3.96.970813232910.2059H-100000@localhost> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 14 Aug 1997 00:11:03 -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>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