From: Coly Li <coly.li@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] mount point is not unique among all nodes
Date: Fri, 13 Feb 2009 14:24:16 +0800 [thread overview]
Message-ID: <49951210.40106@suse.de> (raw)
In-Reply-To: <20090212224347.GC12965@mail.oracle.com>
Joel Becker Wrote:
> On Thu, Feb 12, 2009 at 02:17:40PM -0800, Joel Becker wrote:
>> On Fri, Feb 13, 2009 at 04:09:19AM +0800, Coly Li wrote:
>>> Hi list,
>>>
>>> Here is a bug report on novell bugzilla (https://bugzilla.novell.com/show_bug.cgi?id=456280) that
>>> mount point inside node A can be removed from node B.
>> Can't access the bug.
>>
>>> The problem is, node B does not know an empty dir is be using as mount point on another node. Is
>>> there any solution to return -EBUSY when a dir is be using as mount point on another node ?
>> This is a good question. As of right now, we don't have a way
>> to do it.
>
> Sunil and I took a look. It would seem we need to mark the
> dentry lock LVB with a mountpoint count. That way, ocfs2_unlink() could
> check that right before calling ocfs2_remote_dentry_delete().
> The problem is that the VFS doesn't notify us when one of our
> directories is mounted over. Somewhere in do_add_mount() it would need
> to tell ocfs2 about it, so that ocfs2 could take the EX on the dentry
> lock and bump the mount count in the LVB.
> So, that's what we'll do when we get around to it. I don't
> think it's a high priority; we haven't actually run into this until now.
>
I filed a bug on oracle oss bugzilla, see
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1075
I will continue to follow this issue. Thanks for the feedback.
--
Coly Li
SuSE Labs
next prev parent reply other threads:[~2009-02-13 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 20:09 [Ocfs2-devel] mount point is not unique among all nodes Coly Li
2009-02-12 22:17 ` Joel Becker
2009-02-12 22:43 ` Joel Becker
2009-02-13 6:24 ` Coly Li [this message]
2009-02-12 22:19 ` Sunil Mushran
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=49951210.40106@suse.de \
--to=coly.li@suse.de \
--cc=ocfs2-devel@oss.oracle.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 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.