From owner-freebsd-fs@FreeBSD.ORG Thu Nov 12 19:37:25 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37356106568D for ; Thu, 12 Nov 2009 19:37:25 +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 B29D78FC12 for ; Thu, 12 Nov 2009 19:37:23 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAG/y+0qDaFvJ/2dsb2JhbADdeYQ8BIFs X-IronPort-AV: E=Sophos;i="4.44,730,1249272000"; d="scan'208";a="53658853" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 12 Nov 2009 14:37:22 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id CC937FB80AD; Thu, 12 Nov 2009 14:37:22 -0500 (EST) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kyGCKWF9Ptop; Thu, 12 Nov 2009 14:37:21 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 2CE99FB801A; Thu, 12 Nov 2009 14:37:21 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nACJj4q17144; Thu, 12 Nov 2009 14:45:04 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 12 Nov 2009 14:45:04 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: =?utf-8?B?R2Vycml0IEvDvGhu?= In-Reply-To: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de> Message-ID: References: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1804928587-1258055104=:15244" Cc: freebsd-fs@freebsd.org Subject: Re: nfsv4 FreeBSD server vs. Linux client I/O error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2009 19:37:25 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-1804928587-1258055104=:15244 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 12 Nov 2009, Gerrit K=C3=BChn wrote: > Hi all, > > ist this the right place to talk about nfsv4 issues, or does this better > go to -net (or even somewhere else)? > > Anyways, I'll start here and now: > I have a FreeBSD8-RC2 server which I set up for nfsv4 serving according > to nfsv4(4). I have a Linux client (Kernel 2.6.25) trying to do > "mount.nfs4 / /mnt -v". This takes *exactly* 30s. (looks like running int= o > some kind of timeout). After that, the mount is there. It is displayed by > "mount" and gives the right sizes with "du -h". > However, as soon as I try to access /mnt with "cd /mnt" or "ls /mnt" I ge= t > an Input/Output Error on the client side. > A few things to check on the server: - Did you add a "V4:" line to your /etc/exports and what did you set as the root path in it? If you used "V4: /" then the root file system would need to be exported by another line in /etc/exports for it to work. - If you are only exporting another filesystem, lets say "/exports", then your mount command would have to look like: =09mount -t nfs4 /exports /mnt (assuming "V4: /" was used) - If you used "V4: /exports", then "mount -t nfs4 :/ /mnt" would work and you would see /exports at /mnt. Beyond something like the above, if you capture packets using "tcpdump -s 0 -w host " on the server and then email me "", I can take a look at it. (tcpdump doesn't know diddly about NFSv4, but wireshark does and can handle tcpdump captures.) > Googleing around I found only very few information about nfsv4 and FreeBS= D > (ok, it's a new feature after all :-). Does anyone here already have some > experiences to share? Anyone already using FreeBSD servers against Linux > clients? Any suggestions how to debug and solve the problem above? > I don't usually test against Linux, but I'll try a quick mount here, in case something is obviously broken. rick ---559023410-1804928587-1258055104=:15244--