From: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] nfs4: 30 second delay during umount of remote fs on system shutdown
Date: Fri, 29 Feb 2008 02:03:05 +0100 [thread overview]
Message-ID: <200802290203.06241.elendil@planet.nl> (raw)
In-Reply-To: <1204235218.7109.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Thursday 28 February 2008, Trond Myklebust wrote:
> On Thu, 2008-02-28 at 18:29 +0100, Frans Pop wrote:
> > I have verified that portmap is also not running during S31umountnfs.sh
> > with 2.6.24, so apparently there has been a change in the kernel that
> > has made umount look for portmap and cause the 30 second delay if it is
> > not running.
>
> You are probably seeing the effect of lockd going down: it always
> attempts to unregister from the portmapper (and no, this is _not_ new
> behaviour).
It is _very much_ new behavior because as soon as I boot (and shut down)
with a 2.6.24 kernel the problem completely disappears. Userland is *100%
identical* between my tests.
> If debian is killing the portmapper while lockd is still up, then that
> is a definite debian bug...
I have no idea about that. AFAICT lockd is not even running (at least,
there's no process named lockd, even when the system is running normally.
Isn't lockd an nfs3 thing? I'm using nfs4 here.
Cheers,
FJP
WARNING: multiple messages have this Message-ID (diff)
From: Frans Pop <elendil@planet.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] nfs4: 30 second delay during umount of remote fs on system shutdown
Date: Fri, 29 Feb 2008 02:03:05 +0100 [thread overview]
Message-ID: <200802290203.06241.elendil@planet.nl> (raw)
In-Reply-To: <1204235218.7109.13.camel@heimdal.trondhjem.org>
On Thursday 28 February 2008, Trond Myklebust wrote:
> On Thu, 2008-02-28 at 18:29 +0100, Frans Pop wrote:
> > I have verified that portmap is also not running during S31umountnfs.sh
> > with 2.6.24, so apparently there has been a change in the kernel that
> > has made umount look for portmap and cause the 30 second delay if it is
> > not running.
>
> You are probably seeing the effect of lockd going down: it always
> attempts to unregister from the portmapper (and no, this is _not_ new
> behaviour).
It is _very much_ new behavior because as soon as I boot (and shut down)
with a 2.6.24 kernel the problem completely disappears. Userland is *100%
identical* between my tests.
> If debian is killing the portmapper while lockd is still up, then that
> is a definite debian bug...
I have no idea about that. AFAICT lockd is not even running (at least,
there's no process named lockd, even when the system is running normally.
Isn't lockd an nfs3 thing? I'm using nfs4 here.
Cheers,
FJP
next prev parent reply other threads:[~2008-02-29 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 17:29 [regression] nfs4: 30 second delay during umount of remote fs on system shutdown Frans Pop
[not found] ` <200802281829.16343.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2008-02-28 21:46 ` Trond Myklebust
2008-02-28 21:46 ` Trond Myklebust
[not found] ` <1204235218.7109.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-29 1:03 ` Frans Pop [this message]
2008-02-29 1:03 ` Frans Pop
[not found] ` <200802290203.06241.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2008-02-29 1:09 ` Jeff Layton
2008-02-29 1:09 ` Jeff Layton
2008-02-29 4:55 ` Trond Myklebust
2008-02-29 4:55 ` Trond Myklebust
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=200802290203.06241.elendil@planet.nl \
--to=elendil-eibgga6/0yrmr6xm/wnwpw@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.