Date: Thu, 12 Nov 2009 14:45:04 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: =?utf-8?B?R2Vycml0IEvDvGhu?= <gerrit@pmp.uni-hannover.de> Cc: freebsd-fs@freebsd.org Subject: Re: nfsv4 FreeBSD server vs. Linux client I/O error Message-ID: <Pine.GSO.4.63.0911121436150.15244@muncher.cs.uoguelph.ca> In-Reply-To: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de> References: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <server>/exports /mnt (assuming "V4: /" was used) - If you used "V4: /exports", then "mount -t nfs4 <server>:/ /mnt" would work and you would see /exports at /mnt. Beyond something like the above, if you capture packets using "tcpdump -s 0 -w <file> host <server>" on the server and then email me "<file>", 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0911121436150.15244>