public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Salmon <salmr0@bp.com>
To: Barry Naujok <bnaujok@sgi.com>
Cc: David Chinner <dgc@sgi.com>, Ralf Gross <Ralf-Lists@ralfgross.de>,
	xfs@oss.sgi.com
Subject: Re: xfs_rapair memory requirement per TB
Date: Thu, 24 Jan 2008 09:50:16 -0600	[thread overview]
Message-ID: <1201189816.32649.358.camel@holwrs01.bp.com> (raw)
In-Reply-To: <op.t5euakap3jf8g2@pc-bnaujok.melbourne.sgi.com>





> >> >
> >> > 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.
> 
> Yes, quite a few memory improvements have been made.
> 
> Right now, I can repair a 9TB filesystem with ~150 million inodes
> in 2GB of RAM without going to swap using xfs_repair 2.9.4 and
> with no custom/tuning/config options.




Thanks. That is great news about the memory improvements.  We currently
run SLES 10 SP1 which comes with:

hpcxe005:# xfs_repair -V
xfs_repair version 2.8.16

others come with:

hpcxe001:~ # xfs_repair -V
xfs_repair version 2.9.2


Did the memory improvements make it into 2.8.16? How about 2.9.2? If not
i take it we can download the latest source and just have the 2.9.4
xfs_repair binary laying around in case we ever need to use it.  Would
using a 2.9.4 xfs_repair binary on a 2.8.16 created xfs file system
cause any problems?

Thanks
Rene

> 

  reply	other threads:[~2008-01-24 15:50 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
2008-01-24  1:26       ` Barry Naujok
2008-01-24 15:50         ` Rene Salmon [this message]
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=1201189816.32649.358.camel@holwrs01.bp.com \
    --to=salmr0@bp.com \
    --cc=Ralf-Lists@ralfgross.de \
    --cc=bnaujok@sgi.com \
    --cc=dgc@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