From owner-freebsd-current@FreeBSD.ORG Fri Jan 7 14:47:17 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 980D61065675; Fri, 7 Jan 2011 14:47:17 +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 258408FC1A; Fri, 7 Jan 2011 14:47:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAPe1Jk2DaFvO/2dsb2JhbACDd6EjrjmNYoEhgzd0BIRnhiI X-IronPort-AV: E=Sophos;i="4.60,289,1291611600"; d="scan'208";a="104582331" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 07 Jan 2011 09:47:16 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 58ADBB3F86; Fri, 7 Jan 2011 09:47:16 -0500 (EST) Date: Fri, 7 Jan 2011 09:47:16 -0500 (EST) From: Rick Macklem To: Marek Salwerowicz Message-ID: <1543154155.235420.1294411636305.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4d26f9a20813d5.52450662@wp.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: Garrett Cooper , freebsd-current@freebsd.org, Garrett Cooper Subject: Re: nfssvc not available or version mismatch (nfsv4 client) 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: Fri, 07 Jan 2011 14:47:17 -0000 > > Try loading all of the modules one-by-one. > > so, after loading nfssvc.ko: > > vm-salwerom% sudo ./nfsuserd start > Starting nfsuserd. > vm-salwerom% sudo ./nfscbd start > Starting nfscbd. > nfscbd: Can't get fully qualified host name This won't break the nfscbd, which you don't need unless you are using delegations. (Not enabled by default in the FreeBSD server.) However, in nfsuserd can't figure out your domain, you'll need to set one via the "-domain xxx.yyy" option for nfsuserd. What it needs to know is the domain name that you are using for bind, etc since that is appended to user and group names that go on the wire. For example: - If the machine's name is nfs-client.cis.uoguelph.ca as shown by the hostname command... --> the domain name is cis.uoguelph.ca then the user rick will go on the wire as rick@cis.uoguelph.ca - if your hostname doesn't have a domain spec, it will try and get a fully qualified name via the ai_canonname returned from getaddrinfo. For example: # hostname nfs-client <-- no .xxx domain spec so --> does a getaddrinfo for nfs-client and then looks for .xxx in ai_canonname If you do "ls -l" on an NFSv4 mounted directory and see lotts nobody this domain spec either isn't configured or isn't configured the same as the server. > vm-salwerom% kldstat > Id Refs Address Size Name > 1 29 0xffffffff80100000 711d58 kernel > 2 1 0xffffffff80812000 85d0 procfs.ko > 3 2 0xffffffff8081b000 9628 pseudofs.ko > 4 1 0xffffffff80825000 68ad0 if_em.ko > 5 1 0xffffffff80a12000 2c92 geom_md.ko > 6 1 0xffffffff80a15000 50fb tmpfs.ko > 7 1 0xffffffff80a1b000 1fa green_saver.ko > 8 3 0xffffffff80a1c000 381 nfssvc.ko > 9 2 0xffffffff80a1d000 fd24 nfscommon.ko > 10 1 0xffffffff80a2d000 2df67 nfscl.ko > vm-salwerom% > > I am able to mount via nfsv4: > > vm-salwerom% mount_nfs -o nfsv4 free:/home/stud/salwerom nfs > vm-salwerom% mount > 194.29.146.3:/ on / (nfs, read-only) > devfs on /dev (devfs, local) > /dev/md0 on /etc (ufs, local) > procfs on /proc (procfs, local) > tmpfs on /tmp (tmpfs, local) > tmpfs on /var (tmpfs, local) > tmpfs on /home/stud/salwerom (tmpfs, local) > free:/home/stud/salwerom on /home/stud/salwerom/nfs (newnfs) > vm-salwerom% > > > The problem is how to automatically load during system boot > nfssvc(.ko) ? > Hmm, everything seems ok in head and works for me, but it might have been broken at some point. As a workaround, you can build your kernel with options NFSCL in the kernel config file so that it doesn't need to load the modules at all. rick