From: Mike Waychison <mike@waychison.com>
To: Michael Buesch <fsdeveloper@yahoo.de>
Cc: Zeev Fisher <Zeev.Fisher@il.marvell.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: processes stuck in D state
Date: Mon, 5 May 2003 11:24:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0305051122190.20491-100000@bunny.augustahouse.net> (raw)
In-Reply-To: <200305051656.32048.fsdeveloper@yahoo.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1692 bytes --]
On Mon, 5 May 2003, Michael Buesch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Monday 05 May 2003 07:52, Zeev Fisher wrote:
> > Hi!
>
> Hi Zeev!
>
> > I got a continuos problem of unkillable processes stuck in D state (
> > uninterruptable sleep ) on my Linux servers.
> > It happens randomly every time on other server on another process ( all
> > the servers are configured the same with 2.4.18-10 kernel ). Here's an
> > example :
> [snip]
> > Has anyone noticed the same behavior ? Is this a well known problem ?
>
> I've had the same problem with some 2.4.21-preX twice (or maybe more times,
> don't remember) on one of my machines.
> IMHO it has something to do with NFS. (I'm using this box as a NFS-client).
> I wish, I could reproduce it one more time, to do some traces, etc
> on it. But I've not found a way to reproduce it, yet.
>
This happens when you mount an NFS mount with the 'hard' option (default)
and a mount's handle expires incorrectly (eg: server crash).
Read the mount manpage for an explanation to the downsides of using
the 'soft' option.
Mike Waychison
> - --
> Regards Michael Büsch
> http://www.8ung.at/tuxsoft
> 16:50:44 up 52 min, 1 user, load average: 1.00, 1.00, 0.94
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+tnugoxoigfggmSgRAt8BAJ0deufnL/E6acpz4pIPZll8f48TIgCfWmcI
> auSRmi6oyrTbqMVe+MrfuV4=
> =ahIZ
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-05-05 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 5:52 processes stuck in D state Zeev Fisher
2003-05-05 14:56 ` Michael Buesch
2003-05-05 15:24 ` Mike Waychison [this message]
2003-05-05 16:25 ` Michael Buesch
2003-05-05 22:12 ` jw schultz
-- strict thread matches above, loose matches on Subject: below --
2001-04-04 15:47 Pau Aliagas
2001-04-07 22:07 ` Barry K. Nathan
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=Pine.LNX.4.33.0305051122190.20491-100000@bunny.augustahouse.net \
--to=mike@waychison.com \
--cc=Zeev.Fisher@il.marvell.com \
--cc=fsdeveloper@yahoo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).