From: Dave Chinner <david@fromorbit.com>
To: Velimir Galic <veli.galic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair - segemnation fault | git error
Date: Sat, 11 Aug 2012 08:53:10 +1000 [thread overview]
Message-ID: <20120810225310.GG2877@dastard> (raw)
In-Reply-To: <CADcDJaR52zwL+aMaUuQTvbYx2d11LRmzdURE2Ok8z0tKsYTv8A@mail.gmail.com>
On Fri, Aug 10, 2012 at 10:23:03AM +0200, Velimir Galic wrote:
> hi Guys,
>
> I hope you are able to help me, because i think that i
> tried everything that i know off to repair my raid after a disk failure.
>
> Systemspecs:
>
> - HP N40L
> - CPU: AMD Turion II @ 1,5GHZ
> - 8GB ECC RAM
> - Disks:
> - 250GB | OS
> - 4x2GB | RAID 5 | Softraid
> - OS: Openmediavault @ 3.0.20 (last version)
>
>
> Problem:
>
> In my raid a disk was fault so mdadm kicked the disk out of the raid. I put
> a replacement in the box and started a resync of the raid and than
> is happened, a second disk got lost in the raid. The raidsync wasn't
Ok, so you've lost a good chunk of the filesystem then? I don't lik
eto say it, but double disk failures tend to result in unrecoverable
data loss. Given the contents of this email, I know you don't have
backups to restore from, so you might be left with only bits and
pieces even if a repair can be made to run successfully.
> finished and now i'm fighting 3 weeks or more i don't no any more :-( to
> repair the file system.
>
> I tried a lot of different versions of xfs_repair (2.9.4, 2.9.8, 2.10.2,
> 3.0.4, 3.1.2, 3.1.6, 3.1,8), but every precompiled version got an
> "segmentation fault" or hung at phase 3 with 100% cpu load for few day. I
> also tried different distros like ubuntu, debian, redhat, gentoo (yes, i'm
> a little bit desperate :-) ) Than i tried the git version and at first it
> looked good but than i got an another error but i don't understand what the
> problem is.
Perhaps you should tell us whatthe error is. i.e. attach the output
of xfs_repair when it fails.
>
> tried options without any luck: xfs_repair -v -P | xfs_repair -v -P -m 6144
> | xfs_repair -v -P -L
>
> Metadump of the filesystem isn't possible at this moment,
Why not?
> but i could
> bootup a live cd and give it a try with it. I'm pretty stuck and don't no
> what to do any more.
Run your compiled, unstripped xfs-repair binary under gdb and when
it segfaults, dump of the stack trace. That will at least tell use
where it is failing....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-10 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 8:23 xfs_repair - segemnation fault | git error Velimir Galic
2012-08-10 22:53 ` Dave Chinner [this message]
2012-08-11 10:57 ` Michael Monnerie
2012-08-13 11:58 ` Velimir Galic
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=20120810225310.GG2877@dastard \
--to=david@fromorbit.com \
--cc=veli.galic@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox