From owner-freebsd-current Tue Mar 25 16:34:46 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D4A437B401 for ; Tue, 25 Mar 2003 16:34:44 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id DCA9143FAF for ; Tue, 25 Mar 2003 16:34:42 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Mar 2003 00:34:40 +0000 (GMT) To: Patric Mrawek Cc: current@freebsd.org Subject: Re: NFS -current In-Reply-To: Your message of "Tue, 25 Mar 2003 22:01:52 +0100." <20030325210152.GA12565@argv.de> Date: Wed, 26 Mar 2003 00:34:40 +0000 From: Ian Dowse Message-ID: <200303260034.aa92057@salmon.maths.tcd.ie> X-Spam-Status: No, hits=-9.8 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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