|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:29:07 -0500|
|Cc:||Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx|
|References:||<BE5986C67D271E4EA72B61F406AB91F29C7C86@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <429E7FDA.7070307@xxxxxxx> <Pine.LNX.4.58.0506021444230.18757@xxxxxxxxxxxxxxxxxx> <429F0753.5010403@xxxxxxx>|
|User-agent:||Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513)|
Steve Lord wrote:
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.
OK, got that backwards, inode64 says do not keep them in 32 bits, inode32 says keep them in 32 bits.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: False No space left on device error, Eric Sandeen|
|Next by Date:||Re: False No space left on device error, Eric Sandeen|
|Previous by Thread:||Re: False No space left on device error, Steve Lord|
|Next by Thread:||Re: False No space left on device error, Eric Sandeen|
|Indexes:||[Date] [Thread] [Top] [All Lists]|