xfs
[Top] [All Lists]

Re: False No space left on device error

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

well, the inode64 option itself is the -inverse- of the hack, actually, right. Default XFS inode allocation changed a few years ago, to force inodes into the low 32-bit range. THAT was the mild hack, and the inode64 option was added to again allow XFS to work as originally designed, allocating inodes anywhere on the filesystem on systems which could handle 64-bit inodes.


-Eric


Steve



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