From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id E893B29DF8 for ; Thu, 9 May 2013 17:37:27 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay3.corp.sgi.com (Postfix) with ESMTP id 63C91AC00C for ; Thu, 9 May 2013 15:37:27 -0700 (PDT) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id 2G1RFxC6VbwYJinz for ; Thu, 09 May 2013 15:37:25 -0700 (PDT) Date: Fri, 10 May 2013 08:37:24 +1000 From: Dave Chinner Subject: Re: Xfs_repair segfaults. Message-ID: <20130509223724.GS24635@dastard> References: <5187BF8A.2040303@sandeen.net> <5188FF88.6000508@sandeen.net> <20130508233910.GL24635@dastard> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Filippo Stenico Cc: Eric Sandeen , xfs@oss.sgi.com On Thu, May 09, 2013 at 05:11:13PM +0200, Filippo Stenico wrote: > On Thu, May 9, 2013 at 1:39 AM, Dave Chinner wrote: > > > On Wed, May 08, 2013 at 07:30:05PM +0200, Filippo Stenico wrote: > > > Hello, > > > -m option seems not to handle the excessive memory consumption I ran > > into. > > > I actually ran xfs_repair -vv -m1750 and looking into kern.log it seems > > > that xfs_repair invoked oom killer, but was killed itself ( !! ) > > > > That's exactly what the oom killer is supposed to do. > > > > Yeah, some sacrifice needed. > > > > > This is last try to reproduce segfault: > > > xfs_repair -vv -P -m1750 > > > > I know your filesystem is around 7TB in size, but how much RAM do > > you have? It's not unusual for xfs_repair to require many GB of > > memory to run succesfully on filesystems of this size... > > > > it is around 11 TB, 7.2 used. > I have 4 G ram, but xfs_repair -vv -m1 says I need 1558 > root@ws1000:~# xfs_repair -vv -P -m 1 /dev/mapper/vg0-lv0 > Phase 1 - find and verify superblock... > - max_mem = 1024, icount = 29711040, imem = 116058, dblock = > 2927886336, dmem = 1429632 > Required memory for repair is greater that the maximum specified > with the -m option. Please increase it to at least 1558. That's the minimum it requires to run in prefetch mode, not the maximum it will use. 4GB RAM on a badly corrupted 7TB filesystem is almost certainly not enough memory to track all the broken bits that need tracking. Add 20-30GB of swap space and see how it goes... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs