From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 7127F29E15 for ; Wed, 8 May 2013 18:39:26 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay1.corp.sgi.com (Postfix) with ESMTP id 4EC058F8064 for ; Wed, 8 May 2013 16:39:26 -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 2h30DGz7Y35qMDNk for ; Wed, 08 May 2013 16:39:21 -0700 (PDT) Date: Thu, 9 May 2013 09:39:10 +1000 From: Dave Chinner Subject: Re: Xfs_repair segfaults. Message-ID: <20130508233910.GL24635@dastard> References: <5187BF8A.2040303@sandeen.net> <5188FF88.6000508@sandeen.net> 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 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. > 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... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs