public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Ralf Gross <Ralf-Lists@ralfgross.de>
Cc: Barry Naujok <bnaujok@sgi.com>, xfs@oss.sgi.com
Subject: Re: xfs_rapair memory requirement per TB
Date: Thu, 24 Jan 2008 11:28:28 +1100	[thread overview]
Message-ID: <20080124002828.GC155259@sgi.com> (raw)
In-Reply-To: <20080123085339.GB12435@p15145560.pureserver.info>

On Wed, Jan 23, 2008 at 09:53:39AM +0100, Ralf Gross wrote:
> Barry Naujok schrieb:
> > >
> > >Reading the "Repairing a possibly incomplete xfs_growfs command?" thread
> > >this month makes me wonder if there is some type of rough formula or
> > >guesstimation cheat sheet to figure out how much memory and swap one
> > >would need for an xfs_repair given a file system with many terabytes.
> > >
> > >
> > >Say I have an 8TB LUN that needs an xfs_repair.  What would be the rough
> > >memory requirements and swap space?
> > >
> > 
> > General rule of thumb at the moment is 128MB of RAM/TB of filesystem
> > plus 4MB/million inodes on that filesystem.
> 
> Did this change lately? I found the rule of thumb: 2 GB RAM for 1 TB
> of disk storage + some RAM per x inodes.

The above is based on actual theoretical usage, the below:

> http://oss.sgi.com/archives/xfs/2005-08/msg00045.html

was based on reported usage on during live repair runs.

I think Barry discovered the difference to be things external
to repair such as heap fragmentation and has since corrected
the worst of the issues so requirements are, in general,
much closer to the theoretical numbers now.

Cheers,

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

  reply	other threads:[~2008-01-24  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 23:01 xfs_rapair memory requirement per TB Rene Salmon
2008-01-23  2:51 ` Barry Naujok
2008-01-23  8:53   ` Ralf Gross
2008-01-24  0:28     ` David Chinner [this message]
2008-01-24  1:26       ` Barry Naujok
2008-01-24 15:50         ` Rene Salmon
2008-01-24 16:07           ` Ralf Gross
2008-01-25  0:01           ` Barry Naujok

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=20080124002828.GC155259@sgi.com \
    --to=dgc@sgi.com \
    --cc=Ralf-Lists@ralfgross.de \
    --cc=bnaujok@sgi.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