From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Velimir Galic <veli.galic@gmail.com>
Subject: Re: xfs_repair - segemnation fault | git error
Date: Sat, 11 Aug 2012 12:57:21 +0200 [thread overview]
Message-ID: <1488479.ZDGdaNpFNb@saturn> (raw)
In-Reply-To: <CADcDJaR52zwL+aMaUuQTvbYx2d11LRmzdURE2Ok8z0tKsYTv8A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]
Am Freitag, 10. August 2012, 10:23:03 schrieb Velimir Galic:
> a second disk got lost in the raid. The raidsync wasn't finished and
> now i'm fighting 3 weeks or more i don't no any more :-( to repair
> the file system.
How far did the recovery go when it broke? If it was on 10% when the 2nd
disk broke, you can stop to try to get anything. If it was 90% finished,
you might have a chance...
> 4x2GB | RAID 5 | Softraid
This is a 6GB net RAID 5 device? Which devices?
> I tried a lot of different versions of xfs_repair
I hope you got a copy of all disks before you even tried to repair?
Otherwise it might be too late now, when repair wrote something on that
device.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-11 10:57 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
2012-08-11 10:57 ` Michael Monnerie [this message]
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=1488479.ZDGdaNpFNb@saturn \
--to=michael.monnerie@is.it-management.at \
--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 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.