From: Ben Greear <greearb@candelatech.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: is 'umount' asynchronous?
Date: Tue, 07 Sep 2010 17:12:17 -0700 [thread overview]
Message-ID: <4C86D4E1.4000403@candelatech.com> (raw)
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.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-09-08 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:12 Ben Greear [this message]
2010-09-08 17:19 ` is 'umount' asynchronous? J. Bruce Fields
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=4C86D4E1.4000403@candelatech.com \
--to=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 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.