[Top] [All Lists]

Re: inode64

To: Jerzy Borkowski <jubork@xxxxxxxxxxxxx>
Subject: Re: inode64
From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
Date: Tue, 19 May 2015 12:05:43 -0300
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <555B4E53.8050908@xxxxxxxxxxxxx>
Mail-followup-to: Jerzy Borkowski <jubork@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
References: <4D4BF051.9000608@xxxxxxxxxxxxx> <555B4E53.8050908@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)

If you use inode64, the inodes will be spread all along the disk. The inode
numbers are created based on its location in the disk, so, if you have a disk
which is larger than 1TB, you can have inode numbers larger than 32bit which you

If you want to keep inodes in the range you mentioned, you must need inode32
options, so no inode will be allocated beyond the 32 bits limit which you

But, since you have a 800GB filesystem, and not a filesystem larger than 1TB,
you can use inode64 and you will still have inodes in the 32bit range, but, if
in any circunstance you grow the filesystem, you'll have inodes being allocated
beyond that.

if you must keep inode allocations in the 32bit range, I suggest you using the
inode32 option, to avoid any future problems in case of a grow of the

On Tue, May 19, 2015 at 04:53:07PM +0200, Jerzy Borkowski wrote:
> Hi,
> If an 800GB XFS filesystem is mounted with inode64 option,
> is it guaranteed that all inodes in the filesystem are in
> the range 0-0xFFFFFFFF ?
> Kernel is 3.17.x
> Thanks,
> Jurek
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs


<Prev in Thread] Current Thread [Next in Thread>
  • inode64, Jerzy Borkowski
    • Re: inode64, Carlos Maiolino <=