From owner-freebsd-fs@FreeBSD.ORG Thu Dec 20 22:48:00 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10438424 for ; Thu, 20 Dec 2012 22:48:00 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id BE74D8FC14 for ; Thu, 20 Dec 2012 22:47:59 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EACeV01CDaFvO/2dsb2JhbABCAw6GLLdMc4IeAQEEASNWBRYOCgICDRkCWQYTiA0GpWyTFYEijEqCG4ETA4hijSmQSII2XIIE X-IronPort-AV: E=Sophos;i="4.84,326,1355115600"; d="scan'208";a="5636577" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 20 Dec 2012 17:47:58 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 879A9B3F16; Thu, 20 Dec 2012 17:47:58 -0500 (EST) Date: Thu, 20 Dec 2012 17:47:58 -0500 (EST) From: Rick Macklem To: Tim Gustafson Message-ID: <1258576329.1531397.1356043678539.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NFS Problems MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Linux)/6.0.10_GA_2692) Cc: FreeBSD Filesystems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 22:48:00 -0000 Tim Gustafson wrote: > > Yep. Using Kerberos for NFS is really orthogonal to NFSv4. The only > > reason some people tie the two together is that the NFSv4.0 RFC > > required > > support for RPCSEC_GSS (which is what sec=krb5 does). Although > > support > > for AUTH_SYS wasn't required I believe all NFSv4 servers do support > > it > > and I know it works for FreeBSD. > > > > Just do the mounts without sec=krb5 and you'll be using NFSv4.0 over > > AUTH_SYS (which is the old uid + gid list stuff NFS has always > > used). > > Ok, I'm trying to go down this path, but I'm running into some > trouble. For my test, I am using a FreeBSD file server and a FreeBSD > client. On the server, in /etc/rc.conf, I have: > > rpcbind_enable="yes" > nfs_server_enable="yes" > mountd_flags="-r -l" > nfsd_enable="yes" > mountd_enable="yes" > rpc_lockd_enable="no" > rpc_statd_enable="no" > nfs_server_flags="-t -n 128" > nfsv4_server_enable="yes" > nfsuserd_enable="yes" > > And in /etc/exports, I have: > > V4: /export -network 192.168.0.0 -mask 255.255.255.0 > You must also export the /export file system. The "V4:" just pegs where the root is for NFSv4, it does not actually export any file systems. The /export line is the same as you would have for NFSv3. Something like: /export -alldirs -network 192.168.0.0 -mask 255.255.255.0 Check in /var/log/messages for any errors in /etc/exports. > And then on the client, in /etc/fstab, I have: > > server:/ /mnt nfs rw,nfsv4,late 0 0 > > I can mount /mnt with no problem, but when I change into that folder > and attempt to do anything, either as the superuser or as a regular > user, I get: > > tjg@client: cd /mnt/home/tjg > tjg@client: touch foo > touch: foo: Input/output error > > I know that it is "sorta" working, because if I attempt to cd to a > folder that doesn't exist on the server, I get a different error: > > tjg@client: ls -al /mnt/home/tjg > total 0 > tjg@client: ls -al /mnt/home/foo > ls: /mnt/home/foo: No such file or directory > > I'm sure that I'm missing a basic configuration option, but I can't > find it. > > -- > > Tim Gustafson > tjg@soe.ucsc.edu > 831-459-5354 > Baskin Engineering, Room 313A