public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS daemons in D state for 2 minutes at shutdown
Date: 20 Sep 2001 19:15:21 +0200	[thread overview]
Message-ID: <shswv2tpyvq.fsf@charged.uio.no> (raw)
In-Reply-To: <3531863216.20010920164639@port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: VDA's message of "Thu, 20 Sep 2001 16:46:39 +0300"

>>>>> " " == VDA  <VDA@port.imtp.ilyichevsk.odessa.ua> writes:

     > Hi NFS folks, I am still fighting witn nfsd/lockd not dying
     > upon killall5.  (they are stuck in D state for 2 mins and then
     > die with "rpciod: active tasks at shutdown?!" at console)

     > I found out that nfsd and lockd die as expected when I use
     > modified killall5 which do not SIGSTOP all tasks before killing
     > them.

     > Any idea why this makes such difference? Is this a bug in
     > nfsd/lockd or in killall5?

killall5 is a bad idea as a method for killing nfsd/lockd. You are
better off using something more targeted so you can ensure the correct
ordering.
If you kill the portmapper before the nfs/lockd daemons have finished
unregistering their services then the above behaviour is completely
normal.

Cheers,
  Trond

  reply	other threads:[~2001-09-20 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 13:46 NFS daemons in D state for 2 minutes at shutdown VDA
2001-09-20 17:15 ` Trond Myklebust [this message]
2001-09-21  8:01   ` VDA
2001-09-21  9:25     ` Trond Myklebust
2001-09-21 12:46       ` VDA
2001-09-21 23:06         ` Trond Myklebust
2001-09-22  0:36           ` Mike Castle

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=shswv2tpyvq.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --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