[Top] [All Lists]

Re: xfs_rapair memory requirement per TB

To: Ralf Gross <Ralf-Lists@xxxxxxxxxxxx>
Subject: Re: xfs_rapair memory requirement per TB
From: David Chinner <dgc@xxxxxxx>
Date: Thu, 24 Jan 2008 11:28:28 +1100
Cc: Barry Naujok <bnaujok@xxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20080123085339.GB12435@p15145560.pureserver.info>
References: <1201042882.32649.256.camel@holwrs01.bp.com> <op.t5c3kfub3jf8g2@pc-bnaujok.melbourne.sgi.com> <20080123085339.GB12435@p15145560.pureserver.info>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/
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.


Dave Chinner
Principal Engineer
SGI Australian Software Group

<Prev in Thread] Current Thread [Next in Thread>