linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Keegan <lk@pfw.demon.co.uk>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, <neilb@suse.de>,
	<linux-nfs@vger.kernel.org>
Subject: Re: race-free exportfs and unmount?
Date: Sat, 22 Mar 2014 10:11:04 +0000	[thread overview]
Message-ID: <20140322101104.56dd99a0@cs3.al.itld> (raw)
In-Reply-To: <532CA76B.8050300@windriver.com>

On Fri, 21 Mar 2014 14:56:11 -0600
Chris Friesen <chris.friesen@windriver.com> wrote:
> On 03/21/2014 02:20 PM, J. Bruce Fields wrote:
> > On Fri, Mar 21, 2014 at 02:17:13PM -0600, Chris Friesen wrote:
> >>
> >> Hi,
> >>
> >> There was a linux-nfs thread in July 2012 with the subject "Linux
> >> NFS and cached properties".  It discussed the fact that you can't
> >> reliably do
> >>
> >> exportfs -u 192.168.1.11:/mnt

You forgot echo /mnt > /proc/fs/nfsd/unlock_filesystem

> >> umount /mnt
> >>
> >> since there could be rpc users still running when exportfs returns,
> >> so the umount fails thinking the filesystem is busy.

This is almost always the case on an active NFS server. Stuff 'em! Just
unlock the filesystem and your drbd flip should work just fine. I've
been doing it for years.

BOFH.

  reply	other threads:[~2014-03-22 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 20:17 race-free exportfs and unmount? Chris Friesen
2014-03-21 20:20 ` J. Bruce Fields
2014-03-21 20:56   ` Chris Friesen
2014-03-22 10:11     ` Larry Keegan [this message]
2014-03-21 22:58   ` Chris Friesen
2014-03-21 23:09     ` NeilBrown

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=20140322101104.56dd99a0@cs3.al.itld \
    --to=lk@pfw.demon.co.uk \
    --cc=bfields@fieldses.org \
    --cc=chris.friesen@windriver.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).