From: Dave Chinner <david@fromorbit.com>
To: "Łukasz Korczyk" <korczyk.l@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: question about xfs_repair
Date: Mon, 4 Jul 2011 22:13:07 +1000 [thread overview]
Message-ID: <20110704121307.GX561@dastard> (raw)
In-Reply-To: <CAHyte2beL-dkGJa=tFy2DV+reYqPSTVH-VOPyRdPZMaho7Hh4Q@mail.gmail.com>
On Mon, Jul 04, 2011 at 11:41:49AM +0200, Łukasz Korczyk wrote:
> Helo
>
> I have a question I wasn't able to find answer for.
>
> Which factors influence memory usage of xfs_repair?
> Does any formula exist to count possible memory usage?
# xfs_repair -n -vv -m 1 /dev/vda
Phase 1 - find and verify superblock...
- max_mem = 1024, icount = 64, imem = 0, dblock = 4294967296, dmem = 2097152
Required memory for repair is greater that the maximum specified
with the -m option. Please increase it to at least 2096.
So it's telling me I need at least 2096MB of RAM to repair my 16TB
filesystem, of which 2097152KB is needed for tracking free space...
I just added 50 million inodes to the filesystem (it now has 50M +
10 inodes in it), and the result is:
# xfs_repair -vv -m 1 /dev/vda
Phase 1 - find and verify superblock...
- max_mem = 1024, icount = 50401792, imem = 196882, dblock = 4294967296, dmem = 2097152
Required memory for repair is greater that the maximum specified
with the -m option. Please increase it to at least 2289.
That is now needs at least another 200MB of RAM to run.
It is worth noting that these numbers are the absolute minimum
required and repair may require more RAM than this to complete
successfully. If you only give it this much RAM, it will be slow;
for best repair performance, the more RAM you can give it the
better.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-04 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 9:41 question about xfs_repair Łukasz Korczyk
2011-07-04 12:13 ` Dave Chinner [this message]
2011-07-05 10:43 ` Łukasz Korczyk
2012-04-06 14:21 ` Kolega z pracy :*
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=20110704121307.GX561@dastard \
--to=david@fromorbit.com \
--cc=korczyk.l@gmail.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