Date: Wed, 26 Mar 2003 00:34:40 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: Patric Mrawek <patric@argv.de> Cc: current@freebsd.org Subject: Re: NFS -current Message-ID: <200303260034.aa92057@salmon.maths.tcd.ie> In-Reply-To: Your message of "Tue, 25 Mar 2003 22:01:52 %2B0100." <20030325210152.GA12565@argv.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030325210152.GA12565@argv.de>, Patric Mrawek writes: >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 I'm not sure what you mean by a "lost" mount. Do all further accesses to the filesystem hang? 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. 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? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303260034.aa92057>