On Wed, Aug 10, 2005 at 08:10:45AM +1200, Steve Wray wrote:
> David Chinner wrote:
> > On Tue, Aug 09, 2005 at 02:56:28AM +0200, djani22@xxxxxxxxxxxxx wrote:
> >>More info:
> >>I try xfs_check and xfs_ncheck (and more progs) with +200GB swap, but no
> >>less than 1 second and get : out of memory.
> > Your filesystem (8TiB) may simply bee too large for your system to
> > be able to repair. Try mounting it on a 64bit system with more RAM
> > in it and repairing it from there.
> Sorry, but is this a joke?
A joke? Absolutely not.
Acheivable XFS filesystem sizes outgrew the capability of 32 bit
Irix systems to repair them several years ago. Now that linux
supports larger than 2TiB filesystems on 32 bit systems, this is
true for Linux as well.
FWIW, look at the irix man pages for xfs_check and xfs_repair:
A quote so you don't have to follow the links:
xfs_repair is an n32 binary and will run on all Irix platforms. However,
when repairing a multi-terabyte filesystem, the memory requirements
exceed what is available to n32 binaries. For those filesystems,
xfs_repair64, 64-bit binary, should be used.
This has also been mentioned before on this list in similar circumstances:
As for moving disks to other machines to repair them - that's not
unusual, either. e.g:
> Surely xfs could/should have a repair mode that actually works on the
> hardware that the filesystem is installed on?
Surely it could. When can we expect a patch? ;)
> Alternatively, so that others can avoid the situation of having to go
> and get their hands on a 64 bit machine to repair their xfs filesystems,
> is there a cutoff point heuristic? Ie: how big does an xfs filesystem
> have to be for it to require a 64 bit architecture to fix?
From some quick tests I just ran, for 32bit binaries xfs_check needs
around 1GiB RAM per TiB of filesystem plus about 100MiB RAM per
1million inodes in the filesystem (more if you have lots of
fragmented files). Double this for 64bit binaries. e.g. it took
1.5GiB RAM for 32bit xfs_check and 2.7GiB RAM for a 64bit
xfs_check on a 1.1TiB filesystem with 3million inodes in it.
For xfs_repair, there is no one-size fits all formula as memory
consumption depends not only on the size of the filesystem but what
is in the filesystem, how it is laid out, what is corrupted in the
filesystem, etc. For example, the filesystem I checked above only
required ~150MiB for repair to run but that is a consistent
filesystem. I've seen equivalently size filesystems (~1TiB)
take close to 1GiB of RAM to repair when they've been significantly
Sorry I can't be more precise than this, but it should give you
some idea of what to expect....
R&D Software Enginner
SGI Australian Software Group