XFS memory recomendation?

Michael Monnerie michael.monnerie at is.it-management.at
Sun Feb 19 07:16:32 CST 2012


Am Freitag, 17. Februar 2012, 18:17:46 schrieb Eric Sandeen:
> http://xfs.org/index.php/XFS_FAQ#Q:_Which_factors_influence_the_memory
> _usage_of_xfs_repair.3F

I tried that, and it said "use 434":

xfs_repair -n -vv -m 1 /dev/mapper/vg_orion-lv_orion_data 
Phase 1 - find and verify superblock...
        - max_mem = 1024, icount = 339648, imem = 1326, dblock = 
805304256, dmem = 393214
Required memory for repair is greater that the maximum specified with 
the -m option. Please increase it to at least 434.

But when I tried with 
# xfs_repair -n -vv -m 434 /dev/mapper/vg_orion-lv_orion_data 
it said the same again. It only worked with 435:
# xfs_repair -n -vv -m 435 /dev/mapper/vg_orion-lv_orion_data 
(is that what you call an off-by-1 error?)

Maybe that has been fixed already? This is
# xfs_repair -V
xfs_repair Version 3.1.6

BTW, this XFS is 3219644160 KB (3,2TB), used 2,9TB, has (df -i) 325364 
inodes used, 293884 files in 31643 dirs. It seems mem usage primarily 
comes from inodes, not from the size of the filesystem.

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20120219/6e63f479/attachment.sig>


More information about the xfs mailing list