From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Mon, 8 Jun 2009 12:12:13 -0400 Subject: [Cluster-devel] Re: GFS2: Allow all meta/normal mount combinations In-Reply-To: <1244211463.29604.698.camel@localhost.localdomain> References: <1244209936.29604.696.camel@localhost.localdomain> <20090605140918.GA14060@infradead.org> <1244211463.29604.698.camel@localhost.localdomain> Message-ID: <20090608161213.GA20881@infradead.org> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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.