linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: houlinfei <hou.linfei@h3c.com>,
	"bfields@fieldses.org" <bfields@fieldses.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: neilb@suse.com, SteveD@redhat.com, Kinglong Mee <kinglongmee@gmail.com>
Subject: Re: some problems about permission of subdirectory
Date: Sun, 26 Feb 2017 08:23:19 +0800	[thread overview]
Message-ID: <4ee0f1c3-0f80-6e66-9db3-3c1382cde6d6@gmail.com> (raw)
In-Reply-To: <780a867d.53cc0e.15a75733ad0.Coremail.hou.linfei@h3c.com>

On 2/25/2017 21:26, houlinfei wrote:
> hi Kinglong, Bruce,
> Two suggestions all can resolve the problem,but when i use the way of mount --bind /root/hh/hh1 /root/hh/hh1 , and client has mount this nfs share. When i umount /root/hh/hh1.It will busy. when i umount share on client and stop nfsd on server. Then i can umount /root/hh/hh1. Why?

Yes, that's a old problem.

For each export entry, nfsd has some cache in kernel,each valid cache
has a reference to the export directory.
The umount operation finds that and report busy, after stop the service,
all cache will be dropped(no any reference to export entry), umount success.

I have try to fix the problem at 2015, 
http://www.spinics.net/lists/linux-nfs/msg52646.html

Ps, if someone think it's really a requirement, I will pick it up?

thanks,
Kinglong Mee

  reply	other threads:[~2017-02-26  0:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 13:26 some problems about permission of subdirectory houlinfei
2017-02-26  0:23 ` Kinglong Mee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-25  9:44 houlinfei
2017-02-25 10:51 ` Kinglong Mee
2017-02-23 15:21 houlinfei
2017-02-23  3:53 houlinfei
2017-02-23  8:18 ` Kinglong Mee
2017-02-22  7:16 houlinfei
2017-02-22  8:00 ` Kinglong Mee
2017-02-21  8:52 houlinfei
2017-02-21 13:50 ` Kinglong Mee
2017-02-24 19:14   ` J. Bruce Fields
2017-02-25 10:45     ` Kinglong Mee

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=4ee0f1c3-0f80-6e66-9db3-3c1382cde6d6@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=SteveD@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=hou.linfei@h3c.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.com \
    /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).