From: Chris Friesen <chris.friesen@windriver.com>
To: <linux-kernel@vger.kernel.org>
Subject: [bug?] can't unmount filesystem after running "exportfs -u" -- dangling refcount?
Date: Fri, 21 Mar 2014 10:37:44 -0600 [thread overview]
Message-ID: <532C6AD8.6000406@windriver.com> (raw)
I'm seeing some odd behaviour on an NFS server.
We're running 3.4.82 and have a drbd-replicated filesystem
(active/standby) that is exported via NFS (explicitly v3, and
/proc/fs/nfsd is mounted).
On a server switchover we take down the NFS server IP address, run
"exportfs -u" on the exports, unmount the drbd filesystem, and then
demote drbd from primary to secondary.
The problem we're seeing is that sometimes "exportfs -u" completes
successfully but "umount" fails with an error that the filesystem is
busy. When this happens, "fuser" doesn't see any userspace users, which
points at the kernel thinking it has a reference open.
When it's in the stuck state, manually running "exportfs -f" seems to
resolve the issue so that "unmount" can run.
Are there any known issue in this area?
I'm not currently subscribed to the list, so please CC me on replies.
Thanks,
Chris
reply other threads:[~2014-03-21 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=532C6AD8.6000406@windriver.com \
--to=chris.friesen@windriver.com \
--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