All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Marc Boivin <marc.boivin@libeo.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS segfaulting on xfs_repair
Date: Fri, 20 Dec 2013 09:44:30 -0600	[thread overview]
Message-ID: <20131220154430.GY1935@sgi.com> (raw)
In-Reply-To: <5C03211A-BF4B-485A-97F1-9CE00DACF09D@libeo.com>

Hi Marc,

On Fri, Dec 20, 2013 at 09:26:26AM -0500, Marc Boivin wrote:
>     We’ve been having a hard time with our ifs partition but managed to get
>     it almost back to working conditions. To give you a bit of context we
>     have a LVM sitting on top of 3 RAID 5. The partition is encrypted. We had
>     issues with RAID degradation but now the RAIDs are healthy. 
> 
> We ran xfs_repair quite a few times (5 if I’m not mistaken). We are stuck
> with an error: 
> 
> *** glibc detected *** xfs_repair: malloc(): smallbin double linked list corrupted: 0x00007f5dc7642570 ***
> ======= Backtrace: =========
> /lib/x86_64-linux-gnu/libc.so.6(+0x76d76)[0x7f6149f96d76]
> /lib/x86_64-linux-gnu/libc.so.6(+0x7a658)[0x7f6149f9a658]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x70)[0x7f6149f9bb90]
> xfs_repair[0x42da83]
> xfs_repair[0x42db16]
> xfs_repair[0x42dd62]
> xfs_repair[0x430b74]
> xfs_repair[0x4492de]
> xfs_repair[0x44e634]
> xfs_repair[0x451976]
> xfs_repair[0x44c4ba]
> xfs_repair[0x41f126]
> xfs_repair[0x421e55]
> xfs_repair[0x4039d8]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f6149f3eead]
> xfs_repair[0x403ff9]

I think if you install the xfsprogs debuginfo package this backtrace will
include function names.  Do you have a core file?  What version of xfs_repair?

Thanks,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-12-20 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 14:26 XFS segfaulting on xfs_repair Marc Boivin
2013-12-20 15:44 ` Ben Myers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131220154430.GY1935@sgi.com \
    --to=bpm@sgi.com \
    --cc=marc.boivin@libeo.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.