Date: Tue, 9 Aug 2005 12:08:23 +1000
From: David Chinner <dgc@sgi.com>
To: djani22@dynamicweb.hu
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS repair problem
Message-ID: <20050809120823.E13484145@melbourne.sgi.com>
References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <005301c59c7d$2eedab20$0400a8c0@LocalHost>; from djani22@dynamicweb.hu on Tue, Aug 09, 2005 at 02:56:28AM +0200
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Status: O
Content-Length: 1126
Lines: 36

On Tue, Aug 09, 2005 at 02:56:28AM +0200, djani22@dynamicweb.hu wrote:
> More info:
> 
> I try xfs_check and xfs_ncheck (and more progs) with +200GB swap, but no
> different!
> less than 1 second and get : out of memory.

Swap won't help if you're running an ia32 (32bit) kernel - you have
a per-process memory limit of 1-4GiB (depending on kernel and
config).  The amount of physical memory and swap does not change
this limitation.

> It really looks like BUG!

Expected behaviour. It's documented in the xfs_check(8) man page.

> 2 months before when I try xfs_check with "only" 2TB, and only 2GB ram
> system, it works!

Memory consumption of the various xfs userspace tools is related to
the size of the filesystem and the number of inodes in it. The
larger the filesystem and the larger the number of inodes it has
in it, the more memory is required to repair it.

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.

Cheers,

Dave.
-- 
Dave Chinner
R&D Software Enginner
SGI Australian Software Group