From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Eric Sandeen <sandeen@redhat.com>,
stan@hardwarefreak.com, "Assarsson,
Emil" <Emil.Assarsson@sonyericsson.com>
Subject: Re: XFS memory recomendation?
Date: Sun, 19 Feb 2012 14:16:32 +0100 [thread overview]
Message-ID: <5722408.cXkY2gHLh8@saturn> (raw)
In-Reply-To: <4F3F0A4A.7050708@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1243 bytes --]
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
[-- 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
next prev parent reply other threads:[~2012-02-19 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 11:50 XFS memory recomendation? Assarsson, Emil
2012-02-17 2:49 ` Dave Chinner
2012-02-17 13:05 ` Michael Monnerie
2012-02-17 15:27 ` Assarsson, Emil
2012-02-18 1:14 ` Eric Sandeen
2012-02-18 1:58 ` Stan Hoeppner
2012-02-18 2:17 ` Eric Sandeen
2012-02-19 13:16 ` Michael Monnerie [this message]
2012-02-19 21:00 ` Eric Sandeen
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=5722408.cXkY2gHLh8@saturn \
--to=michael.monnerie@is.it-management.at \
--cc=Emil.Assarsson@sonyericsson.com \
--cc=sandeen@redhat.com \
--cc=stan@hardwarefreak.com \
--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