[Top] [All Lists]

Re: Xfs_repair segfaults.

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: Xfs_repair segfaults.
From: Filippo Stenico <filippo.stenico@xxxxxxxxx>
Date: Thu, 9 May 2013 17:11:13 +0200
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=CG/y1Robj5EVLRNHcidDPWiRhd2ucV0VR8FI5DOupMU=; b=HPSffOFrvsyKVAqkr+fpHIN49vg/YP7Xzrm497gYQofjXAvvE6g0OSrNDSOHIROkeX IkeDHIQOqUk0RAoIhKlKxRcjxFmQ1sZvSdKAccwY2ujsuhK9mJr010rcB/UD1ZPtki3b Z32Rfp79FsxXeAXPHmb5/XSf5WGnB2Lap/fZzL0G6IqgKX0IizrfbltgJs/lvvwlrzuV hQfHCkM6D6JYKpS8+Utt610YnxeJfhHRTIeEVxhPqUo6OD439XgOM2q/F6vw7GNvzoKJ RyCSDK/a7GTcnIPSJPXtGkJG7WVF3zVCap4OC3O26vlOrZoP+a4+l787vQwK+Qe8Wa8a yfhA==
In-reply-to: <20130508233910.GL24635@dastard>
References: <CADNx=KsT9DC=vveyTZx8EovddFx9mhRS-yzygaORHZ_4VyXfzQ@xxxxxxxxxxxxxx> <5187BF8A.2040303@xxxxxxxxxxx> <CADNx=KvZPhbRn9Kc3+KdoAY7jZ3U0uyG6wgUB5vcxX85CkFdQg@xxxxxxxxxxxxxx> <CADNx=Kv0bt3fNGW8Y24GziW9MOO-+b7fBGub4AYP70b5gAegxw@xxxxxxxxxxxxxx> <5188FF88.6000508@xxxxxxxxxxx> <CADNx=KvmA7jgqBUO0YvKddHvFaqxHNZKfF3eWajOW8GWKwNhbA@xxxxxxxxxxxxxx> <CADNx=Kv=7TFkJKom6_JM8B+A6YRckj175TbCcHrTWYL_N-qkYw@xxxxxxxxxxxxxx> <CADNx=KvxtCHEk9G07yS88-casVAXBxRTghV5nGKd_0LtcqpYpQ@xxxxxxxxxxxxxx> <20130508233910.GL24635@dastard>

On Thu, May 9, 2013 at 1:39 AM, Dave Chinner <david@xxxxxxxxxxxxx> 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.

so I figured 1750 megs would be enough


Dave Chinner

xfs mailing list

<Prev in Thread] Current Thread [Next in Thread>