public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: "Daniele P." <daniele@interline.it>
Cc: xfs@oss.sgi.com
Subject: Re: xfsrepair memory consumption
Date: Wed, 21 Mar 2007 09:13:05 +1100	[thread overview]
Message-ID: <20070320221305.GR32602149@melbourne.sgi.com> (raw)
In-Reply-To: <200703201532.06076.daniele@interline.it>

On Tue, Mar 20, 2007 at 03:32:05PM +0100, Daniele P. wrote:
> Hi all,
> I'm just asking if any work has been done/is in progress to improve
> xfs_repair memory consumption.

Work is in progress, but it won't really solve your problem.
See, you've got:

> enceladus:~# df -i /dev/sdb1
> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> /dev/sdb1            293049664 6511481 286538183    3% /media/300

6 million inodes in your filesystem, and a certain points in
repair we have to hold indexes of them all (plus some state) in
memory. Phase 6 is one of these points.

In terms of inode count, I generally use the rule that for every
10million inodes you need a gigabyte of RAM for repair - you needed
about 500MB for 6million inodes.

We have been trimming bits and pieces off this per-inode usage
but there comes a point where you just need more memory. That
is, as filesystem size grows, so does the amount of memory
needed to repair it in a finite time....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-03-20 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 14:32 xfsrepair memory consumption Daniele P.
2007-03-20 22:13 ` David Chinner [this message]
2007-03-20 23:48   ` Barry Naujok
2007-03-21  8:35     ` Daniele P.
2007-03-21  8:34   ` Daniele P.
     [not found] <200703210843.TAA08491@larry.melbourne.sgi.com>
2007-03-21 11:08 ` Daniele P.
2007-03-21 21:36   ` Chris Wedgwood
2007-03-23  8:36     ` Daniele P.

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=20070320221305.GR32602149@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=daniele@interline.it \
    --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