From: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
To: Trond Myklebust
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
Cc: Devel FS Linux
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tao Peng <tao.peng-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
Subject: Re: VFS regression: commit aba809cf0944 breaks MNT_SHRINKABLE automounted partitions
Date: Sat, 30 Aug 2014 00:01:47 +0100 [thread overview]
Message-ID: <20140829230147.GD7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAHQdGtRBqmsfeVVysTnTEELHuwiPwvsyTHtoRAsfSS0aSyCbfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Aug 29, 2014 at 05:47:58PM -0400, Trond Myklebust wrote:
> Note that the issue happens with NFSv4 or NFSv4.1 (not NFSv3).
That's what I'd been using for testing.
> Note that on my system, if I call 'umount' a second time after getting
> the 'device is busy' error, then it succeeds. It looks as if the first
> call to 'umount /mnt' causes the directory /mnt/export to clear,
> causing the second 'umount /mnt' to succeeed (unless I try to access
> /mnt/export again):
Now, that smells like a different bug - see if commit ab8f2c from -next
helps with that one.
Anyway, I think I see what's going on; moreover, I have a kinda-sorta
solution for the current tree, but it's not something that'll be fun
to backport and I'd prefer to look for alternative solutions before going
for that one. Hopefully I'll have something postable by tomorrow morning...
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-29 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 16:27 VFS regression: commit aba809cf0944 breaks MNT_SHRINKABLE automounted partitions Trond Myklebust
[not found] ` <CAHQdGtT4kbPqQvD_fu7c_5_CqK8FCpA5mJsVdh=KxoE9_vXRzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-29 20:58 ` Al Viro
2014-08-29 21:47 ` Trond Myklebust
[not found] ` <CAHQdGtRBqmsfeVVysTnTEELHuwiPwvsyTHtoRAsfSS0aSyCbfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-29 23:01 ` Al Viro [this message]
2014-08-30 0:38 ` Peng Tao
[not found] ` <CAKVebiWBU3du650yeTMfaFuLr=WLUBc2RukFGyBF6Qgxd6zA8Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-30 17:36 ` Al Viro
[not found] ` <20140830173638.GE7996-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2014-08-30 23:27 ` Al Viro
2014-08-31 0:31 ` Peng Tao
2014-08-31 4:09 ` Al Viro
[not found] ` <20140831040910.GH7996-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2014-09-01 23:52 ` Dave Chinner
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=20140829230147.GD7996@ZenIV.linux.org.uk \
--to=viro-3bdd1+5odreifsdqtta3olvcufugdwfn@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tao.peng-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).