On Thu, Jan 24, 2013 at 11:14:00AM +1100, Dave Chinner wrote: > On Wed, Jan 23, 2013 at 05:22:44PM -0600, Ben Myers wrote: > > Hi Harry, > > > > On Wed, Jan 23, 2013 at 03:07:42PM -0800, Harry Edmon wrote: > > > It appears that "mount -o inode32 /dev/sda1 /mnt" ignores the > > > inode32 option and mounts with inode64. After the partition is > > > mounted I can do "mount -o remount,inode32 /mnt" and it remounts > > > with inode32. But shouldn't there be a way to do the initial mount > > > with inode32? I am running Linux 3.7.3 on an amd architecture. I > > > would like this option since I am using EMC Networker for backups > > > (yes, I know about the complaints). Thanks. > > > > # mount -o inode32 /dev/sdb1 /mnt/scratch > > # grep /dev/sdb1 /proc/mounts > > /dev/sdb1 /mnt/scratch xfs rw,relatime,attr2,inode64,noquota 0 0 > > # mount -o remount,inode32 /mnt/scratch > > # grep /dev/sdb1 /proc/mounts > > /dev/sdb1 /mnt/scratch xfs rw,relatime,attr2,inode32,noquota 0 0 > > > > We'll get this fixed. > > That's not necessarily broken. Filesystems under 1TB will always > report inode64. filesytsems will only switch to inode32 (regardless > of the mount option) when they go above the size that will cause > inodes to exceed 32 bits. FWIW, the remount behaviour displayed above is arguably the bug being displayed - it's the new feature, and it doesn't check whether inode numbers can exceed 32 bits like a real mount does - it just blindly changes the behaviour whether or not it is needed.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
