From owner-freebsd-current Tue Nov 17 12:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04754 for freebsd-current-outgoing; Tue, 17 Nov 1998 12:05:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA04748 for ; Tue, 17 Nov 1998 12:05:24 -0800 (PST) (envelope-from yds@ingress.net) Received: (qmail 29147 invoked from network); 17 Nov 1998 20:04:57 -0000 Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31) by paris.dppl.com with SMTP; 17 Nov 1998 20:04:57 -0000 Message-ID: <018001be1265$8cf95560$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: "Tom Bartol" , Subject: Re: NFS problems in -current Date: Tue, 17 Nov 1998 15:04:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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? I remember having this problem very consistently when 2.2.7 came out. Doesn't happen to me anymore. Most likely cuz the network here got rearranged rather than there being any fix in FreeBSD's NFS code. I'm also curious how to diagnose and report something useful should this happen again. -- Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message