Date: Wed, 26 Mar 2003 10:38:12 +0100 From: Patric Mrawek <patric@argv.de> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: current@freebsd.org Subject: Re: NFS -current Message-ID: <20030326093812.GA16614@argv.de> In-Reply-To: <200303260034.aa92057@salmon.maths.tcd.ie> References: <20030325210152.GA12565@argv.de> <200303260034.aa92057@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Dowse wrote: > >On several clients (-DP1, -DP2, 4-stable) mounting a nfs-share > >(mount_nfs -i -U -3 server:/nfs /mnt) and then copying data from that > >share to the local disk (find -x -d /mnt | cpio -pdumv /local) results > >in lost NFS-mount. > > > >client kernel: nfs server server:/nfs: not responding 10 > 9 >=20 > I'm not sure what you mean by a "lost" mount. Do all further accesses > to the filesystem hang? I meant there's no response from the nfs-server. I can interrupt the =BBfind | cpio=AB and restart it. When restarting directly after that it will hang too, but if I wait for about 30 seconds and restart it, the same amount of data is copied. > It is normal enough to get the above 'not responding' errors > occasionally on a busy fileserver, but only if they are almost > immediately followed by 'is alive again' messages. There's only one client and the server isn't busy. > If the filesystem stops working and doesn't recover, could you run > `tcpdump -nepX -s 1600 udp port 2049' when it hangs and record a > few packets? I'll send you private email. (Doing the same on an loopback mounted filesystem on the server itself works fine.) Patric --=20 The problem with troubleshooting is that trouble shoots back.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030326093812.GA16614>