Message-ID: <440485E7.4090702@cfl.rr.com>
Date: Tue, 28 Feb 2006 12:18:31 -0500
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Christoph Hellwig <hch@infradead.org>,
       Steven Whitehouse <swhiteho@redhat.com>, Andrew Morton <akpm@osdl.org>,
       David Teigland <teigland@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [0/16]
References: <1140792511.6400.707.camel@quoit.chygwyn.com> <20060224213553.GA8817@infradead.org>
In-Reply-To: <20060224213553.GA8817@infradead.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1472
Lines: 28

I'm a bit confused.  Why exactly is this unacceptable, and what exactly 
do you propose instead?  Having an entirely separate mount point that is 
sort of parallel to the main one, but with extra metadata exposed?  So 
instead of /path/to/foo/.gfs2_admin/metafile you'd prefer having a 
separate mount point like /proc/fs/gfs/path/to/foo/metafile?


Christoph Hellwig wrote:
>>  b) The .gfs2_admin directory exposes the internal files that GFS uses
>>     to store various bits of file system related information. This means
>>     that we've been able to remove virtually all the ioctl() calls from
>>     GFS2. There is one ioctl() call left which relates to
>>     getting/setting GFS2 specific flags on files. The various GFS2 tools
>>     will be updated in due course to use this new interface.
> 
> Without even looking at the code a strong NACK here.  This is polluting
> the namespace which is not acceptable.  Please implement a second
> filesystem type gfsmeta to do this kind of admin work.  Search for ext2meta
> which did something similar.  Or use a completely different approach,
> I'd need to look at the actual functionality provided to give a better
> advice, but currently I'm lacking the time for that.
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/