All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: <bfields@fieldses.org>, <neilb@suse.de>, <linux-nfs@vger.kernel.org>
Subject: race-free exportfs and unmount?
Date: Fri, 21 Mar 2014 14:17:13 -0600	[thread overview]
Message-ID: <532C9E49.2030007@windriver.com> (raw)


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
umount /mnt

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

I'm running into this on a production system.

Was anything ever done to resolve this issue?
If not are there any workarounds?

Please cc me, I'm not subscribed to the list.

Chris

             reply	other threads:[~2014-03-21 20:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 20:17 Chris Friesen [this message]
2014-03-21 20:20 ` race-free exportfs and unmount? J. Bruce Fields
2014-03-21 20:56   ` Chris Friesen
2014-03-22 10:11     ` Larry Keegan
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=532C9E49.2030007@windriver.com \
    --to=chris.friesen@windriver.com \
    --cc=bfields@fieldses.org \
    --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 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.