From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: GFS2: Allow all meta/normal mount combinations
Date: Mon, 08 Jun 2009 17:17:24 +0100 [thread overview]
Message-ID: <1244477844.29604.784.camel@localhost.localdomain> (raw)
In-Reply-To: <20090608161213.GA20881@infradead.org>
Hi,
On Mon, 2009-06-08 at 12:12 -0400, Christoph Hellwig wrote:
> On Fri, Jun 05, 2009 at 03:17:43PM +0100, Steven Whitehouse wrote:
> > > This is pretty ugly. Even if this is how the old gfs2meta filesystem
> > > worked I would prefer to only allow it if mounted as type gfs2meta, not
> > > for normal gfs2 mount and gradually phase it out.
> > >
> > Which bit is ugly? We need to be able to do this to be sure that we can
> > get a metafs which exactly matches the "normal" fs without races I
> > think. Thats a requirement of the userland tools, unfortunately.
>
> Well, the block device from /proc/self/mounts really is a unique
> key you can get.
>
> If you really insist on using a path to a file make sure that normal
> mounts only take the block device, and meta mounts only take the file.
>
> But even with that it's not a very clear interface.
>
Yes, ok. I think I'll drop this patch for now then. Using the block
device does seem to work ok, and we'd need to update the tools to for
the "file" based method.
We can update the tools to pass a device I think by parsing /proc/mounts
for the path of the "real" filesystem and then using the device entry to
pass to mount. That should solve the problem without needing to add this
patch,
Steve.
prev parent reply other threads:[~2009-06-08 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:52 [Cluster-devel] GFS2: Allow all meta/normal mount combinations Steven Whitehouse
2009-06-05 14:09 ` [Cluster-devel] " Christoph Hellwig
2009-06-05 14:17 ` Steven Whitehouse
2009-06-08 16:12 ` Christoph Hellwig
2009-06-08 16:17 ` Steven Whitehouse [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=1244477844.29604.784.camel@localhost.localdomain \
--to=swhiteho@redhat.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