xfs
[Top] [All Lists]

Re: reducing imaxpct on linux

To: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Subject: Re: reducing imaxpct on linux
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 12 Nov 2010 16:42:40 -0600
Cc: "CZEH, Istvan" <iczeh@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <201011121618.09040@xxxxxx>
References: <1289561141.20961.24.camel@sekli> <201011121401.52477@xxxxxx> <1289571841.20961.44.camel@sekli> <201011121618.09040@xxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.3
On 11/12/2010 09:18 AM, Michael Monnerie wrote:
> On Freitag, 12. November 2010 CZEH, Istvan wrote:
>> I already made the things written in the FAQ (question 32.) but still
>> having the problem. Maybe I should find the oldest data again? It
>> won't be easy...
> 
> I guess the FAQ is a bit wrong here:
> 
> http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_receive_No_space_left_on_device_after_xfs_growfs.3F
> 
> Because it is not the "oldest" data, but the data that is within the 
> space in the first TeraByte of the partition.
> 
> Dave Chinner explained to me, that XFS will split data equally amongst 
> all AGs. So if you have a partition with 4TB and 4 AGs, and you put 1TB 
> data on that partition, each AG will have around 250GB data, meaining 
> you still have 750GB free within the first TB.
> When you do NOT use the inode64 option, all inodes will be placed in the 
> first TB *only*. Even when later you use the inode64 option, it might 
> not succeed in finding space for the inodes.

I don't think that follows; when you mount with inode64, inodes can
be allocated anywhere.  Even if you previously mounted without it.

What is required, though, is some contiguous space to allocate an
inode cluster into.  That could be the problem.

-Eric

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