From: Dave Chinner <david@fromorbit.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question regarding xfs_repair / memory requirement.
Date: Tue, 21 Dec 2010 09:26:53 +1100 [thread overview]
Message-ID: <20101220222653.GL5193@dastard> (raw)
In-Reply-To: <alpine.DEB.2.00.1012200519230.26485@p34.internal.lan>
On Mon, Dec 20, 2010 at 05:20:18AM -0500, Justin Piszcz wrote:
> Hi,
>
> 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?
$ dd if=/dev/zero of=/mnt/scratch/test.img bs=1048576 count=1 seek=50000000
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00463602 s, 226 MB/s
$ ls -lh /mnt/scratch/test.img
-rw-r--r-- 1 dave dave 48T Dec 21 09:22 /mnt/scratch/test.img
$ sudo mkfs.xfs -d name=/mnt/scratch/test.img,file,size=43t
[sudo] password for dave:
meta-data=/mnt/scratch/test.img isize=256 agcount=43, agsize=268435455 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=11542724565, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
$ sudo xfs_repair -m 1 -vv /mnt/scratch/test.img
Phase 1 - find and verify superblock...
- max_mem = 1024, icount = 64, imem = 0, dblock = 11542724565, dmem = 5636095
Required memory for repair is greater that the maximum specified with the -m option. Please increase it to at least 5552
$
Not taking inodes into account, you'll need at least 5.5GB of RAM to run
xfs_repair on a 43TB filesystem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-12-20 22:25 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
2010-12-20 22:26 ` Dave Chinner [this message]
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=20101220222653.GL5193@dastard \
--to=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.