From owner-freebsd-current@FreeBSD.ORG Sun Jan 9 18:59:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EC27106566C for ; Sun, 9 Jan 2011 18:59:44 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4038FC17 for ; Sun, 9 Jan 2011 18:59:43 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEALqUKU2DaFvO/2dsb2JhbACEAqEurhiMTYEhgzd0BIRnhiOFKoYH X-IronPort-AV: E=Sophos;i="4.60,296,1291611600"; d="scan'208";a="104745833" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 09 Jan 2011 13:59:43 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 5681AB404C; Sun, 9 Jan 2011 13:59:43 -0500 (EST) Date: Sun, 9 Jan 2011 13:59:43 -0500 (EST) From: Rick Macklem To: Marek Salwerowicz Message-ID: <715043409.18716.1294599583344.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4D29D61E.8040905@iem.pw.edu.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE8 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org, Andrzej Tobola Subject: Re: NFSv4 and pam_mount - mounting user home directories. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2011 18:59:44 -0000 ----- Original Message ----- > > It just worked for me. Try setting the sysctl before starting nfsd. > > If > > you are starting the daemons manually for a kernel that doesn't have > > "options NFSD" do: > > > > # nfsuserd > > # mountd -e -r > > # sysctl vfs.newnfs.server_min_nfsvers=4 > > # nfsd -e -u -t -n 8 > > > > - mountd -e loads the module, so you can do the sysctl after that > > and before > > starting the nfsd. (Or build a kernel with "options NFSD" and do > > the sysctl > > anytime before starting the nfsd.) > > > > rick > > ps: I tested the FreeBSD-8 client. Other clients may not even talk > > to the NFS > > server during mounting. For those, the mount would succeed, but > > subsequent > > use of the mount won't work. > I tested it on 8.1 Release (GENERIC) i386 (two VMs): > > server: > /etc/rc.conf: > #nfsv4_server_enable="YES" > #nfs_server_enable="YES" > #nfsuserd_enable="YES" > > made modification in /etc/exports: > V4: /usr -sec=sys -network 192.168.183.0 -mask 255.255.255.0 > /usr/home -sec=sys -network 192.168.183.0 -mask 255.255.255.0 > > nfs4-server# nfsuserd > nfs4-server# mountd -e -r > nfs4-server# sysctl vfs.newnfs.server_min_nfsvers=4 > vfs.newnfs.server_min_nfsvers: 2 -> 4 > nfs4-server# nfsd -e -u -t -n 8 > nfs4-server# > > but now client is unable to mount both nfsv4 and nfsv3: > > nfs4-client# mount_nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4/ > [tcp] 192.168.183.131:/home: nfsd: RPCPROG_NFS: RPC: Remote system > error > - Connection refused Again, it works for me (using a pretty current FreeBSD client). The only difference is that I never run mount_nfs directly and would use the following command: # mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4 Assuming the client is a FreeBSD8 box on the 192.168.183.0 subnet, I don't know why it wouldn't work, except that I'd suggest trying the command the way I type it, in case that runs it with somewhat different options? rick