Date: Fri, 02 Apr 2004 16:46:16 -0800 From: Sean McNeil <sean@mcneil.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-current@freebsd.org Subject: Re: nfs server issues Message-ID: <1080953176.51721.0.camel@server.mcneil.com> In-Reply-To: <20040402163353.GC6724@dan.emsphone.com> References: <1080882894.5980.26.camel@server.mcneil.com> <20040402163353.GC6724@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The problem has been resolved. It was an issue with the hardware checksums done by my NIC. I turned off this feature and it is working great now. Sean On Fri, 2004-04-02 at 08:33, Dan Nelson wrote: > In the last episode (Apr 01), Sean McNeil said: > > I have googled and seen a great deal of talk about FreeBSD nfs client > > issues, but haven't seen anything about server problems. I've now > > tried with a Solaris 2.7, HPUX 11.11, and 2 different Linux boxes and > > I get the same thing happening... > > > > If I mount an nfs partition on any of the above mentioned machines, > > everything works fine until I try to copy a bunch of files over. For > > instance, if I mount it at /mnt and do > > > > cd /localdisk; (cd /mnt; tar cf - .) | tar xvf - > > > > It will lock up hard. Linux is saying > > > > nfs: task xxxx can't get a request slot > > "tcpdump -s0" output might help here, I think. Do it from both > machines and make sure no packets are being dropped, and then check to > see what NFS request the client is trying to make that isn't getting > processed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1080953176.51721.0.camel>