From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: is 'umount' asynchronous?
Date: Wed, 8 Sep 2010 13:19:54 -0400 [thread overview]
Message-ID: <20100908171954.GA31634@fieldses.org> (raw)
In-Reply-To: <4C86D4E1.4000403@candelatech.com>
On Tue, Sep 07, 2010 at 05:12:17PM -0700, Ben Greear wrote:
> While testing NFSv4 over TCPv6 on 2.6.36-rc3 + my srcaddr= patch today,
> I noticed that I was getting 'busy' errors from umount if I closed a
> file in a program and then had it immediately system("umount ...");
>
> If I retry the umount a few times, it will start returning 'already unmounted'.
> It took around 50-100ms (I was sleeping 50ms between umount attempts).
>
> Is that expected behaviour? Seems we never needed any retries and never
> got 'busy' on 2.6.34 and earlier.
I've had this:
# ARGH: getting a spurious EBUSY on some
# umounts; this helps:
sleep 1;
in my test scripts for a while, and haven't tried to investigate why
it's happening. (Checking git logs: I added that in July 2008.)
--b.
prev parent reply other threads:[~2010-09-08 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:12 is 'umount' asynchronous? Ben Greear
2010-09-08 17:19 ` J. Bruce Fields [this message]
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=20100908171954.GA31634@fieldses.org \
--to=bfields@fieldses.org \
--cc=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox