From: Frans Pop <elendil@planet.nl>
To: linux-nfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [regression] nfs4: 30 second delay during umount of remote fs on system shutdown
Date: Thu, 28 Feb 2008 18:29:15 +0100 [thread overview]
Message-ID: <200802281829.16343.elendil@planet.nl> (raw)
With 2.6.25-rc2 and -rc3 I noticed a pause of 30 seconds when my system
(Debian unstable, x86_64) is being shutdown. The cause is the unmounting of
an nfs4 remote file system.
The pause does not happen with 2.6.24. I'm unsure about 2.6.25-rc1 as I was
concentrating on other issues when I was testing that.
I can reproduce the same pause on an active system by stopping portmap
before doing an umount of the filesystem.
The shutdown sequence on my box includes:
K20nfs-common
[...]
S20sendsigs
[...]
S31umountnfs.sh
S32portmap
So it seems that things should be OK (S32portmap is after S31umountnfs.sh),
but in fact portmap has already been killed during S20sendsigs!
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.
Is this a kernel regression?
Cheers,
FJP
next reply other threads:[~2008-02-28 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 17:29 Frans Pop [this message]
[not found] ` <200802281829.16343.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2008-02-28 21:46 ` [regression] nfs4: 30 second delay during umount of remote fs on system shutdown 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
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=200802281829.16343.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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.