From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q2825DKZ193823 for ; Wed, 7 Mar 2012 20:05:13 -0600 Received: from mail.sandeen.net (sandeen.net [63.231.237.45]) by cuda.sgi.com with ESMTP id 6HmfJ55GGdFfJMNK for ; Wed, 07 Mar 2012 18:05:12 -0800 (PST) Message-ID: <4F5813D8.8070305@sandeen.net> Date: Wed, 07 Mar 2012 20:05:12 -0600 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: [PATCH] default to 64 bit inodes & add feature flag References: <4F5798F9.2050809@redhat.com> <20120308013413.GL3592@dastard> In-Reply-To: <20120308013413.GL3592@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: Eric Sandeen , xfs-oss , Dave Chinner , Josef 'Jeff' Sipek On 3/7/12 7:34 PM, Dave Chinner wrote: > On Wed, Mar 07, 2012 at 11:20:57AM -0600, Eric Sandeen wrote: >> From: Dave Chinner >> >> Default to allowing 64-bit inodes on the filesystem. >> >> Add a feature bit to the the superblock to record whether 64 bit inodes have >> been allocated on the filesystem or not. This allows us to reject mounting the >> filesytem with inode32 if 64 bit inodes are present. >> >> Once a 64 bitinode is allocated, the inode64 superblock feature bit will be set. >> Once the superblock feature bit is set, the filesystem will default to 64 bit >> inodes regardless of whether inode64 is specified as a mount option. >> >> To ensure only 32 bit inodes are created, the inode32 mount option must be >> used. If there are already 64 bit inodes as flagged by the superblock feature >> bit, then the inode32 mount will be refused. >> >> Signed-off-by: Dave Chinner >> --- >> >> Passing this along to revive the old discussion ... > > I have no objections to do this. However, the kernel patch is just > the tip of the iceberg when it comes to implementing this. > > Were there patches for userspace support of the feature bit? I don't > recall if there were. I'm thinking that xfs_info needs to output > whether this is set, which means the flag needs to be added to the > xfs geometry ioctls in the kernel. Nope, you just put this patch out as a suggestion, and pointed out that userspace needed updates too. If people are in agreement about this then we can proceed with the rest... -Eric > I'd also think that this should also be made a mkfs option (it will > have to default to "not enabled" for a couple of years until distro > kernels catch up) along with outputting the current value. This > will then require xfstests mkfs filter changes, too. > > We'll also need xfs_check, xfs_db (e.g. the version command) and > xfs_repair knowledge of the new feature bit so they don't think the > superblock is corrupted when this new bit gets set.... > Cheers, > > Dave. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs