From: Jan Hudec <bulb@ucw.cz>
To: linux-kernel@vger.kernel.org
Cc: Jan Hudec <bulb@ucw.cz>, jw schultz <jw@pegasys.ws>,
nfs@lists.sourceforge.net
Subject: Re: Unable to kill processes in D-state
Date: Sun, 6 Oct 2002 19:43:36 +0200 [thread overview]
Message-ID: <20021006174336.GC17170@vagabond> (raw)
In-Reply-To: <20021006170932.GA23134@stud.ntnu.no>
On Sun, Oct 06, 2002 at 07:09:32PM +0200, Thomas Lang?s wrote:
> Jan Hudec:
> > If the shares were successfuly reloaded, then the processes should wake
> > up. If they don't, it's a bug in NFS.
>
> They never wake up, and it happens every time.
>
> > Try to reproduce it (ie. reboot some machine, let it start everything
> > and then restart the autofsd and see if processes lock up) and then talk
> > to NFS maintainers about that.
>
> As I said above, it happens every time we encounter this, ie. it's a bug
> that easy to reproduce (since I added nfs@lists.sourceforge.net to the
> CC-list, I'm going to write some of what's already said in this thread).
>
> Problem:
> Processes entering D-state is unkillable. We have a problem with this
> everytime we restart autofs (which automounts quite a few NFS-shares
> on campus), ie. on our samba-boxes smbd hangs forever after this
> (in D-state). Samba still works, it's just that all the D-state processes
> is unkillable and will remain that way untill we reboot the computer.
> Every D-state process increases the load on the machine, and one of our
> 2-CPU intel-boxes currently remains at 430 (which extremly high for such
> a box).
>
> Solution:
> ? :)
You should probably provide detailed info on your setup (computers,
kernel versions, automounter version etc. - as SubmitingBugs in kernel
source suggests). (And maybe change subject to start with NFS PROBLEM,
so more NFS people notice.)
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Jan Hudec <bulb@ucw.cz>
To: linux-kernel@vger.kernel.org
Cc: Jan Hudec <bulb@ucw.cz>, jw schultz <jw@pegasys.ws>,
nfs@lists.sourceforge.net
Subject: Re: Unable to kill processes in D-state
Date: Sun, 6 Oct 2002 19:43:36 +0200 [thread overview]
Message-ID: <20021006174336.GC17170@vagabond> (raw)
In-Reply-To: <20021006170932.GA23134@stud.ntnu.no>
On Sun, Oct 06, 2002 at 07:09:32PM +0200, Thomas Lang?s wrote:
> Jan Hudec:
> > If the shares were successfuly reloaded, then the processes should wake
> > up. If they don't, it's a bug in NFS.
>
> They never wake up, and it happens every time.
>
> > Try to reproduce it (ie. reboot some machine, let it start everything
> > and then restart the autofsd and see if processes lock up) and then talk
> > to NFS maintainers about that.
>
> As I said above, it happens every time we encounter this, ie. it's a bug
> that easy to reproduce (since I added nfs@lists.sourceforge.net to the
> CC-list, I'm going to write some of what's already said in this thread).
>
> Problem:
> Processes entering D-state is unkillable. We have a problem with this
> everytime we restart autofs (which automounts quite a few NFS-shares
> on campus), ie. on our samba-boxes smbd hangs forever after this
> (in D-state). Samba still works, it's just that all the D-state processes
> is unkillable and will remain that way untill we reboot the computer.
> Every D-state process increases the load on the machine, and one of our
> 2-CPU intel-boxes currently remains at 430 (which extremly high for such
> a box).
>
> Solution:
> ? :)
You should probably provide detailed info on your setup (computers,
kernel versions, automounter version etc. - as SubmitingBugs in kernel
source suggests). (And maybe change subject to start with NFS PROBLEM,
so more NFS people notice.)
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2002-10-06 17:43 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
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 [this message]
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=20021006174336.GC17170@vagabond \
--to=bulb@ucw.cz \
--cc=bulb@vagabond.cybernet.cz \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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.