public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: "CZEH, Istvan" <iczeh@virusbuster.hu>
Cc: xfs@oss.sgi.com
Subject: Re: reducing imaxpct on linux
Date: Fri, 12 Nov 2010 16:18:08 +0100	[thread overview]
Message-ID: <201011121618.09040@zmi.at> (raw)
In-Reply-To: <1289571841.20961.44.camel@sekli>


[-- Attachment #1.1: Type: Text/Plain, Size: 1902 bytes --]

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 can imaginge this would help
1) Run xfs_fsr, if it finds files below 1TB and defrags them to a space 
>1TB, you're lucky
2) use the "noikeep" option before doing what XFS Q32 describes. If you 
remove a large portion of inodes, and later move them back, they should 
be newly allocated, and when you use inode64 then, chances are good the 
go at a place >1TB.
3) Find files that are placed at <1TB. I think some xfs_db magic can do 
that, but I never used it so someone else should say.

Anyway: Dave, I'd like to "repair" the FAQ question 32 to be more 
correct and descriptive, would my description be correct?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
// 
// Haus zu verkaufen: http://zmi.at/langegg/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-11-12 15:16 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 [this message]
2010-11-12 22:42       ` Eric Sandeen
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=201011121618.09040@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=iczeh@virusbuster.hu \
    --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