From owner-freebsd-bugs Tue Sep 12 17:18:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA16768 for bugs-outgoing; Tue, 12 Sep 1995 17:18:06 -0700 Received: from huron.aitken.com (jaitken.async.vt.edu [128.173.18.165]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA16749 for ; Tue, 12 Sep 1995 17:17:56 -0700 Received: (from jaitken@localhost) by huron.aitken.com (8.6.11/8.6.9) id UAA05907 for bugs@freebsd.org; Tue, 12 Sep 1995 20:19:07 -0400 From: Jeff Aitken Message-Id: <199509130019.UAA05907@huron.aitken.com> Subject: problem with df(1) To: bugs@freebsd.org Date: Tue, 12 Sep 1995 20:19:06 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3191 Sender: bugs-owner@freebsd.org Precedence: bulk [I tried using send-pr to send this, but it was returned. I've included the entire error portion of the message so that whoever is responsible for send-pr will know what happened.] Forwarded message: > From jaitken Tue Sep 12 20:05:23 1995 > Date: Tue, 12 Sep 1995 17:03:35 -0700 > From: Mail Delivery Subsystem > Subject: Returned mail: unknown mailer error 2 > Message-Id: <199509130003.RAA15692@freefall.freebsd.org> > To: > MIME-Version: 1.0 > Content-Type: multipart/mixed; boundary="RAA15692.810950615/freefall.freebsd.org" > > This is a MIME-encapsulated message > > --RAA15692.810950615/freefall.freebsd.org > > The original message was received at Tue, 12 Sep 1995 17:03:33 -0700 > from jaitken.async.vt.edu [128.173.18.165] > > ----- The following addresses had delivery problems ----- > "| /usr/local/lib/gnats/queue-pr -q >/dev/null 2>&1" (unrecoverable error) > (expanded from: ) > > ----- Transcript of session follows ----- > 554 "| /usr/local/lib/gnats/queue-pr -q >/dev/null 2>&1"... unknown mailer error 2 > > ----- Original message follows ----- > > --RAA15692.810950615/freefall.freebsd.org > Content-Type: message/rfc822 > > Return-Path: jaitken@vt.edu > Received: from huron.aitken.com (jaitken.async.vt.edu [128.173.18.165]) > by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA15691 > for ; Tue, 12 Sep 1995 17:03:33 -0700 > Received: (from jaitken@localhost) by huron.aitken.com (8.6.11/8.6.9) id UAA03539; Tue, 12 Sep 1995 20:04:49 -0400 > Date: Tue, 12 Sep 1995 20:04:49 -0400 > From: Jeff Aitken > Message-Id: <199509130004.UAA03539@huron.aitken.com> > To: FreeBSD-gnats-submit@freebsd.org > Subject: bug in df(1) > Reply-To: jaitken@vt.edu > X-send-pr-version: 3.2 > > > >Submitter-Id: current-users > >Originator: Jeff Aitken > >Organization: Jeff Aitken > jaitken@vt.edu > >Confidential: no > >Synopsis: df(1) hangs when an NFS server disappears > >Severity: serious > >Priority: > >Category: bin > >Release: FreeBSD 2.0-BUILT-19950603 i386 > >Class: sw-bug > >Environment: > > FreeBSD 2.0.5-RELEASE on a 486 DX2/66 PCI. I mount a single directory > via NFS from an Ultrix 4.4 box on the same subnet. > > >Description: > > If the Ultrix box goes away before I unmount the NFS-mounted filesystem, > the df(1) command hangs. Furthermore, it cannot be killed (not even > kill -9 as root does anything). The df process appears to be stuck in > disk wait; it is listed as follows by ps(1): > > jaitken 2967 0.0 0.1 216 12 p1- D - 0:00.00 (df) > root 2994 0.0 0.1 216 12 v2- D - 0:00.00 (df) > > >How-To-Repeat: > > Mount an NFS filesystem, and remove the NFS server (in my case it was > turned off, but I imagine the same thing would happen if you simply > disconnected it from the network). > > >Fix: > > I have no idea. I'm not so concerned with df hanging as I am with the > fact that I cannot kill the process once it is hung. > > > --RAA15692.810950615/freefall.freebsd.org-- > > -- Jeff Aitken jaitken@vt.edu