From owner-freebsd-hackers Sat Mar 27 9:38: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id C5BAF14D95 for ; Sat, 27 Mar 1999 09:38:05 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id MAA25896; Sat, 27 Mar 1999 12:37:43 -0500 (EST) Message-Id: <199903271737.MAA25896@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: schimken@cs.rpi.edu Subject: More death to nfsiod Date: Sat, 27 Mar 1999 12:37:43 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently performed the upgrade to the machine that we were having NFS toubles with. It is not -STABLE as of yesterday. We are still experiencing weird NFS problems on it, and killing nfsiod still resolves most of them. At the end of this email is a script(1) session deomonstrating some of the problems. I looked at nfsiod, and I have no idea how it works, or even why it is needed. It apparently only consists of a single system call that never returns, nfssvc(NFS_BIOD, NULL); (or similiar). This bug was tickeled by performig the folowing tasks on the NFS mounted directory (NFSv2/UDP from a server of the eaxact same build). First I did a "mkisofs112 -J -o netscape.iso .netscape" .netscape contains about 70M of data, 12209 files, and 38 directories. I tickeled the bug before by using mkisofs112 to create an iso image of ie5.0 (arround 60M, 50 files, no directoreis). None of the mkisofs's have ever finished while nfsiod is running. That caused the symptoms, but resolved after a short time. then I issued a "dd if=/dev/zero bs=7k count=100 of=foo" to test NFS performance (a whopping 60K/s on a full-duplex 100M link). Then I did a "dd if=2megfile of=/dev/null", and that is where the script(1) session starts... Script started on Sat Mar 27 12:10:08 1999 sh-2.02$ inc I'm going to create the standard nmh path for you. [Using existing directory] install-mh: unable to write /cs/crossd/Mail/context: Not a directory inc: [install-mh aborted] sh-2.02$ pwd /amd/stagger/home1/a/crossd sh-2.02$ ls -la /amd/stagger/home1/a/crossd ls: /amd/stagger/home1/a/crossd: Not a directory sh-2.02$ ls . [list of directory] sh-2.02$ df -k . Filesystem 1K-blocks Used Avail Capacity Mounted on stagger:/exports/home1 7874493 4236488 3008046 58% /amd/stagger/home1 sh-2.02$ mount | grep stagger | grep home1 stagger:/exports/home1 on /amd/stagger/home1 sh-2.02$ inc I'm going to create the standard nmh path for you. [Using existing directory] install-mh: unable to write /cs/crossd/Mail/context: Not a directory inc: [install-mh aborted] sh-2.02$ su Password: monica# ps auxww | grep nfsiod root 163 0.0 0.0 208 76 ?? S - 0:00.00 nfsiod -n 4 root 164 0.0 0.0 208 76 ?? I - 0:00.00 nfsiod -n 4 root 165 0.0 0.0 208 76 ?? I - 0:00.00 nfsiod -n 4 root 166 0.0 0.0 208 76 ?? I - 0:00.00 nfsiod -n 4 monica# kill 163 164 165 166 monica# exit sh-2.02$ inc Incorporating new mail into inbox... ?103+ 03/27 Chuck Robey Re: gdb 4.17<