[Top] [All Lists]

Re: False No space left on device error

To: Jan Derfinak <ja@xxxxxxxxxxxx>
Subject: Re: False No space left on device error
From: Steve Lord <lord@xxxxxxx>
Date: Thu, 02 Jun 2005 08:19:15 -0500
Cc: Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0506021444230.18757@alienAngel.home.sk>
References: <BE5986C67D271E4EA72B61F406AB91F29C7C86@sbapexch02.ad.corp.expertcity.com> <429E7FDA.7070307@sgi.com> <Pine.LNX.4.58.0506021444230.18757@alienAngel.home.sk>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513)

ino64 is a test option, it deliberately adds a large number to inode values so that it is possible to test that the inode handling is 64 bit clean without buying a few Tbytes of disk (which would have been very expensive when the code was written). It should not be used outside of testing.

inode64 is a hack to force xfs to keep inodes down in the start of
the filesystem where the inode numbers (which are disk addresses
really) do not overflow 32 bits. This is for systems which cannot
cope with larger inodes. There are also 3rd party backup
applications which barf on large inode numbers, networker was
the one I remember.


Jan Derfinak wrote:
On Wed, 1 Jun 2005, Eric Sandeen wrote:


you can use the undocumented/unsupported/non-production "ino64" option to
force all inodes into 64-bit range, and test them on a (smaller) scratch fs.
I expect that it'll be fine but testing is good.

Can you explain difference between ino64 and inode64 options?
Comments in source says:
"ino64"         /* force inodes into 64-bit range */
"inode64"   /* inodes can be allocated anywhere */

Is it possible to explain it little bit more? There is no info in xfs.txt.



<Prev in Thread] Current Thread [Next in Thread>