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:
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 ******
// Haus zu verkaufen: http://zmi.at/langegg/
Description: This is a digitally signed message part.