From: Eric Sandeen <sandeen@sandeen.net>
To: nanashi <nanashi@otenet.gr>
Cc: xfs@oss.sgi.com
Subject: Re: xfsp_repair segfault (3.1.4 & 3.1.6)
Date: Fri, 04 Nov 2011 10:50:08 -0500 [thread overview]
Message-ID: <4EB409B0.4050302@sandeen.net> (raw)
In-Reply-To: <4EAAED63.9050804@otenet.gr>
On 10/28/11 12:58 PM, nanashi wrote:
> Hi,
>
> I have a corrupted RAID5 xfs filesystem from an intel SS-4000 NAS storage.
> I'm using slackware-current with 2.6.39.3-smp kernel (32bit & 64bit)
> When i try xfs_repair I get
>
> xfs_repair: dir2.c:2133: process_dir2: Assertion `(ino
> !=mp->m_sb.sb_rootino && ino != *parent) || (ino ==
> mp->m_sb.sb_rootino && (ino == *parent || need_root_dotdot == 1))'
>
> I try both x86 and x86_64, I build 3.1.4 and 3.1.6 with DEBUG=-DNDEBUG and both continue but gave me a segfault
>
> [23978.718305] xfs_repair[25800]: segfault at 7fffa1d81ff0 ip 00007f15c1852049 sp 00007fffa257f048 error 6 in libc-2.13.so[7f15c1715000+19b000]
>
> I try xfs_metadump and I get segfault too.
>
> The partition is 2.2TB and I don't have enough space to dd it to an image.
>
> I attach the xfs_repair output before the segfault.
>
> any help is appreciated.
>
A corefile + debug binary would be helpful too...
Argh, if metadump segfaults, that will make things tough.
At least with a core + binary we could see just where it blew up.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-11-04 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 17:58 xfsp_repair segfault (3.1.4 & 3.1.6) nanashi
2011-11-04 15:50 ` Eric Sandeen [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=4EB409B0.4050302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=nanashi@otenet.gr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox