Date: Tue, 17 Nov 1998 10:11:48 -0800 (PST) From: Tom Bartol <bartol@salk.edu> To: freebsd-current@FreeBSD.ORG Subject: NFS problems in -current Message-ID: <Pine.BSF.3.96.981117095644.341A-100000@eccles.salk.edu>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981117095644.341A-100000>