[Gluster-users] Recommended filesystem for GlusterFS bricks.
j.hoogeveen at bluebillywig.com
Mon Jul 8 11:58:40 UTC 2013
XFS advice to use inode64 on disk > 1TB
Q: What is the inode64 mount option for?
By default, with 32bit inodes, XFS places inodes only in the first 1TB of a disk. If you have a disk with 100TB, all inodes will be stuck in the first TB. This can lead to strange things like "disk full" when you still have plenty space free, but there's no more place in the first TB to create a new inode. Also, performance sucks.
To come around this, use the inode64 mount options for filesystems >1TB. Inodes will then be placed in the location where their data is, minimizing disk seeks.
Beware that some old programs might have problems reading 64bit inodes, especially over NFS. Your editor used inode64 for over a year with recent (openSUSE 11.1 and higher) distributions using NFS and Samba without any corruptions, so that might be a recent enough distro.
On Jul 8, 2013, at 1:22 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote:
> On 07/04/2013 02:47 AM, Justin Clift wrote:
>> On 03/07/2013, at 4:31 PM, Kaleb KEITHLEY wrote:
>>> No, but I wouldn't worry about it. The latest results from our performance engineering team show that the default values are generally the best choice.
>>> OTOH, you should mount with inode64 mount option.
>> Interesting. It's probably worth us creating an FAQ entry somewhere on the wiki,
>> recommending good sets of mount options to suit various scenarios.
>> I can write that up. Just need to know what to put in it.
>> For "inode64", when should people use it? "always"? :D
> Yes, always. Perhaps not necessary on small volumes, e.g. < 250GB.
>> Do you have a general set of favourite options you use, that I can start with?
> That's it.
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users