xfs
[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: Eric Sandeen <sandeen@xxxxxxx>
Date: Thu, 02 Jun 2005 08:26:54 -0500
Cc: 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 (Macintosh/20050317)
Jan Derfinak wrote:
On Wed, 1 Jun 2005, Eric Sandeen wrote:

Hi.


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.

i don't know why inode64 is missing.

ino64 is testing only; it artificially forces ALL inodes into 64 bits.

inode64 is for production on 64-bit boxs; it -allows- inodes to grow into 64 bits.

-Eric

Thanks.

Jan



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