Steve Lord wrote:
> Yes, also mkfs has recently been changed to do this automatically, so
> provided someones mkfs has been updated recently enough, this scenario
> should not arise anymore. At least until Linux support 16 Tbyte devices
> at which point the more complex fix is needed.
And if you'd like to check an existing filesystem, the latest xfs_info
will print the current inode size you can expect (the "imaxbits" line).
Also, bear in mind that if you want to grow your filesystem later, you
may hit the inode number size problem again. Doubling your filesystem
size will add one bit to the maximum inode number, on average. So, if
you make a filesystem at 1TB, but anticipate growing it to 4TB, you
should choose an inode size of 1024 or so to give you some room in the
bits.
-Eric
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|