From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Jan Hudec <bulb@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: Unable to kill processes in D-state
Date: Sun, 6 Oct 2002 01:56:14 +0200 [thread overview]
Message-ID: <20021005235614.GC25827@stud.ntnu.no> (raw)
In-Reply-To: <20021005182740.GC16200@vagabond>
Jan Hudec:
> On the other hand it's a bug if a process stays in D-state for time of
> order of seconds or more. Unfortunately it's impossible to avoid this
> in networking filesystems with current state of VFS (in 2.4). Even there
> though, it's a bug if it's indefinite.
Well, it's NFS-related (we use autofs to mount our nfs-shares), and the
processes are staying forever when they have gotten to the D-state.
> These problems were already discussed on LKML, you might want to search
> the archive. IIRC this is a known problem of OpenAFS (not in standart
> kernel). It was reported with various drivers for some 2.4.x kernels
> too.
As you see, we've got this problem with NFS as the filesystem, and
the processes won't die or return, they just hang there setting
the load-number up in the roof.
--
Thomas
next prev parent reply other threads:[~2002-10-06 0:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 9:07 Unable to kill processes in D-state Thomas Langås
2002-10-05 18:11 ` Robert Love
2002-10-05 18:27 ` Jan Hudec
2002-10-05 23:56 ` Thomas Langås [this message]
2002-10-06 2:18 ` jw schultz
2002-10-06 2:37 ` Robert Love
2002-10-06 2:49 ` jw schultz
2002-10-06 10:59 ` Thomas Langås
2002-10-06 12:24 ` jw schultz
2002-10-06 14:36 ` Thomas Langås
2002-10-06 16:42 ` Jan Hudec
2002-10-06 17:09 ` Thomas Langås
2002-10-06 17:43 ` Jan Hudec
2002-10-06 17:43 ` Jan Hudec
2002-10-07 12:24 ` Denis Vlasenko
2002-10-16 0:33 ` Thomas Langås
2002-10-16 0:33 ` Thomas Langås
2002-10-06 14:30 ` Graham Murray
2002-10-06 14:54 ` Thomas Langås
2002-10-06 20:26 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 19:50 Jeremy Sanders
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021005235614.GC25827@stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=bulb@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.