public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question regarding xfs_repair / memory requirement.
Date: Mon, 20 Dec 2010 12:04:17 +0100	[thread overview]
Message-ID: <20101220120417.1a0df133@galadriel.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1012200519230.26485@p34.internal.lan>

Le Mon, 20 Dec 2010 05:20:18 -0500 (EST) vous écriviez:

> I am looking at FS to use for a possible 43TB array.
> If there is a problem with a volume this large, how much ram will 
> xfs_repair need to fsck the volume?
> 

Nothing special, I have tens of such filesystems. With a < 3.0 xfs_progs
you should be able to run xfs_repair with 8 GB of RAM. With newer
versions the memory requirement are even lower.

I often needed at times to run older xfs_repair on big filesystems with
only 1 GB of RAM, and using lots of swap (3, 4 GB or more) did the
trick, though of course it was slow as a caterpillar swimming in
molasses.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-12-20 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 10:20 Question regarding xfs_repair / memory requirement Justin Piszcz
2010-12-20 11:04 ` Emmanuel Florac [this message]
2010-12-20 22:26 ` Dave Chinner

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=20101220120417.1a0df133@galadriel.home \
    --to=eflorac@intellique.com \
    --cc=jpiszcz@lucidpixels.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