From owner-freebsd-current Tue Nov 17 10:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16846 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16838 for ; Tue, 17 Nov 1998 10:11:29 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA25089 for ; Tue, 17 Nov 1998 10:10:33 -0800 (PST) Date: Tue, 17 Nov 1998 10:11:48 -0800 (PST) From: Tom Bartol To: freebsd-current@FreeBSD.ORG Subject: NFS problems in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've been seeing the following problem for a while now (since 3.0-19981006-BETA) but was too busy at the time to report it or help diagnose it further. Now I've got some time on my hands... I can fairly consistently wedge NFS writes to our server with the following: dd if=/dev/zero of=ick bs=8192 count=1000 which tries to write an 8MB file to our file server which is an Auspex. I have mounted Auspex from my 3.0-current machine (cvsupped and built this morning) in NFSv3 mode. This command will wedge one or more of the nfsiod processes. "ps -auwx | grep nfsiod" reports the following: root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 The two processes in state "D" are the wedged ones. A separate machine running -current from July 11 works fine. Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS reads work fine. Is anyone else seeing similar behaviour? What can I do to try to fine tune a diagnosis and help solve the problem? Thanks for your help, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message