From owner-freebsd-questions@FreeBSD.ORG Tue Sep 7 10:31:38 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DF8C1065673 for ; Tue, 7 Sep 2010 10:31:38 +0000 (UTC) (envelope-from ahamiltonwright@mta.ca) Received: from smtpx.mta.ca (smtpx.mta.ca [138.73.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id 724D98FC14 for ; Tue, 7 Sep 2010 10:31:38 +0000 (UTC) Received: from qemg.mta.ca ([138.73.29.51]:49160 helo=qemg.org) by smtpx.mta.ca with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71) (envelope-from ) id 1OsvSi-0002dl-DA; Tue, 07 Sep 2010 07:31:36 -0300 Date: Tue, 7 Sep 2010 07:31:36 -0300 (ADT) From: "A. Wright" To: Bill Tillman In-Reply-To: <168438.41481.qm@web36503.mail.mud.yahoo.com> Message-ID: References: <168438.41481.qm@web36503.mail.mud.yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: ahamiltonwright@mta.ca Cc: "freebsd-questions@freebsd.org" Subject: Re: NFS Issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2010 10:31:38 -0000 On Mon, 6 Sep 2010, Bill Tillman wrote: > I have two LAN segments with a FreeBSD server on each. > > Server A is 10.0.0.254 > Server B is 192.168.0.102 > > I setup server A has two drives and I setup a share on drive #2 to be shared via NFS with the both networks. I also made a symlink on drive #2 to a folder on drive #1 > > On server B I can nfs_mount the share on server A and see the symlink. But when I try to access the files in the symlink it shows the link is broken, In other words no files show up. > > On server A I can see the files in the symlink folder just fine. This is expected NFS behaviour: NFS exports filesystems starting at a given (exported) mount point. While there are many reasons for this, think about the security issues if a user on B could create a symlink on your exported volume (because the origin of the symlink will make no difference to the server) to access any file anywhere on A. If you want both disks 1 and 2 visible, the standard solution is to export and mount both disks on B. If the paths (absolute is easiest, but relative can be made to work) are consistent between A and the mounted image of A's filesystems on B, then your symlinks will work -- that is, if you have this kind of /etc/fstab entry, mounting "/disk1" on A to "/disk1" on B: A:/disk1/somedir /disk1/somedir A:/disk2 /disk2 then a symlink in /disk1/somedir/link pointing to /disk1/something will work just fine. A.