From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 16:40:42 2004 Return-Path: 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 3805816A4CE for ; Mon, 11 Oct 2004 16:40:42 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id A494C43D41 for ; Mon, 11 Oct 2004 16:40:41 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 7D01E36C for ; Mon, 11 Oct 2004 18:40:40 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85035-04 for ; Mon, 11 Oct 2004 18:40:39 +0200 (CEST) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id C1C6A32C for ; Mon, 11 Oct 2004 18:40:39 +0200 (CEST) From: Benjamin Lutz To: freebsd-current@freebsd.org Date: Mon, 11 Oct 2004 18:40:36 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart26796955.qEen7xcciQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410111840.40750.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Subject: NFS trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 16:40:42 -0000 --nextPart26796955.qEen7xcciQ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I'm seeing a lot of processes getting stuck in "nfsfsync" state lately.=20 I'm running FreeBSD 5.3-BETA7, and I've seen this with both the i386 and=20 the amd64 version. As NFS server I'm using a FreeBSD 4.10 machine and an up to date gentoo=20 box (running Linux 2.4.25_pre7-gss-r11). I've mounted the NFS exports with a simple nfs_mount=20 uno:/var/www/localhost www as well as with some options that should make=20 nfs more robust: mount_nfs -D 2 -L -R 2 -i -s -x 3 uno:/var/www/localhost www In all cases, the process has started hanging when writing to the exported= =20 NFS share. This could be a text editor (kate), or cp. Subsequent access=20 (eg, with ls) to the directory where the first process tried to write to=20 will make the second process hang in state "nfs". Nothing gets logged on the server, the client logs this repeatedly: nfs server uno:/var/www/localhost: not responding =46orcibly unmounting the share works and seems to unfreeze the frozen=20 applications. This behaviour is new. I cannot say when exactly I've first seen this, but= =20 I think it must have appeared somewhere between BETA5 and BETA7. What can I do to make NFS work more reliably again? Benjamin --nextPart26796955.qEen7xcciQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBareIgShs4qbRdeQRAr1nAKCDPRrlcc1KccTtZ8TL0JRAcHawDwCeK5JQ xEQCEXxwx+gVlLrqYa+KWtw= =88x5 -----END PGP SIGNATURE----- --nextPart26796955.qEen7xcciQ--