From: Christian Pedaschus <cpedaschus@gmx.de>
To: Jonathan <jrs@abhost.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: data recovery on raid5
Date: Sun, 23 Apr 2006 01:17:09 +0200 [thread overview]
Message-ID: <444AB975.40302@gmx.de> (raw)
In-Reply-To: <444A9841.8070202@abhost.net>
nice to hear you got your data back.
now it's perhaps a good time to donate some money to some
ppls/oss-projects for saving your ass ;) ;)
greets, chris
Jonathan wrote:
> hazel /virtual # mdadm -C /dev/md0 -c 32 -n 4 -l 5
> --parity=left-asymmetric missing /dev/etherd/e0.[023]
> mdadm: /dev/etherd/e0.0 appears to be part of a raid array:
> level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
> mdadm: /dev/etherd/e0.2 appears to be part of a raid array:
> level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
> mdadm: /dev/etherd/e0.3 appears to contain an ext2fs file system
> size=720300416K mtime=Wed Oct 5 16:39:28 2005
> mdadm: /dev/etherd/e0.3 appears to be part of a raid array:
> level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
> Continue creating array? y
> mdadm: array /dev/md0 started.
> hazel /virtual # mount -t ext2 -r /dev/md0 /md0
> hazel /virtual # df -H
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda4 67G 5.8G 58G 10% /
> udev 526M 177k 526M 1% /dev
> /dev/hda3 8.1G 34M 7.7G 1% /tmp
> none 526M 0 526M 0% /dev/shm
> /dev/md1 591G 11G 551G 2% /virtual
> /dev/md0 591G 54G 507G 10% /md0
>
> now I'm doing a:
>
> (cd /md0 && tar cf - . ) | (cd /virtual/recover/ && tar xvfp -)
>
> thank you thank you thank you thank you thank you thank you
>
>
> Molle Bestefich wrote:
>
>> Jonathan wrote:
>>
>>
>>> Well, the block sizes are back to 32k now, but I still had no luck
>>> mounting /dev/md0 once I created the array.
>>>
>>
>>
>> Ahem, I missed something.
>> Sorry, the 'a' was hard to spot.
>>
>> Your array used layout : left-asymmetric, while the superblock you've
>> just created has layout: left-symmetric.
>>
>> Try again, but add the option "--parity=left-asymmetric"
>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2006-04-22 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 18:57 data recovery on raid5 Jonathan
2006-04-22 19:48 ` Molle Bestefich
2006-04-22 20:07 ` Jonathan
2006-04-22 20:22 ` Molle Bestefich
2006-04-22 20:32 ` Jonathan
2006-04-22 20:38 ` Molle Bestefich
2006-04-22 20:55 ` Jonathan
2006-04-22 21:17 ` Molle Bestefich
2006-04-22 21:42 ` Carlos Carvalho
2006-04-22 22:58 ` Molle Bestefich
2006-04-22 22:30 ` David Greaves
2006-04-22 23:17 ` Christian Pedaschus [this message]
2006-04-22 20:51 ` Molle Bestefich
2006-04-22 20:28 ` Carlos Carvalho
2006-04-23 2:46 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 23:11 Sam Hopkins
2006-04-21 23:31 ` Mike Tran
2006-04-21 23:38 ` Mike Hardy
2006-04-22 4:03 ` Molle Bestefich
2006-04-22 7:43 ` David Greaves
2006-04-22 8:51 ` David Greaves
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=444AB975.40302@gmx.de \
--to=cpedaschus@gmx.de \
--cc=jrs@abhost.net \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).