From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: "CZEH, Istvan" <iczeh@virusbuster.hu>, xfs@oss.sgi.com
Subject: Re: reducing imaxpct on linux
Date: Fri, 12 Nov 2010 16:42:40 -0600 [thread overview]
Message-ID: <4CDDC2E0.3060000@sandeen.net> (raw)
In-Reply-To: <201011121618.09040@zmi.at>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-12 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 11:25 reducing imaxpct on linux CZEH, Istvan
2010-11-12 13:01 ` Michael Monnerie
[not found] ` <1289571841.20961.44.camel@sekli>
2010-11-12 15:18 ` Michael Monnerie
2010-11-12 22:42 ` Eric Sandeen [this message]
2010-11-13 15:06 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CDDC2E0.3060000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=iczeh@virusbuster.hu \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox