All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dragon" <Sunghost@gmx.de>
To: linux-raid@vger.kernel.org
Subject: Possible to rescue SW Raid5 with 2 missing Disks
Date: Fri, 08 Feb 2013 10:17:00 +0100	[thread overview]
Message-ID: <20130208091700.256910@gmx.net> (raw)

Hello,

my situation is this: i have 3 server with each of 6x3tb in an sw raid5 on a debian squeeze system. on top of this i use moosefs as a filecluster. the problem now is that for a very short time 2 of the disks failed. at this time there was no file activity only the filesync between the nodes of the cluster.

after that i cant rebuild the raid: "mdadm: /dev/md2 assembled from 4 drives and 1 spare - not enough to start the array."

the superblock seems to be ok. and at least, by an advice from phil turmel, i tried a diffent kind of recreation with these results:

Test1:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c,d,e,f}4
-> filesize 708MB with 20603326 lines and canceling at the end by e2fsck
- bad superblock or partitiontable is damage
- bad checksum of group or descriptor
- lots of invalid inodes
- canceld with lots of illegal blocks in inodes

Test2:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c,d,e}4 missing
-> filesize 1,3GB  with 37614367 lines and canceling by e2fsck at the end
- back to original superblock
- bad superblock or damaged partitiontable at the beginning
- lots of invalid inodes
- canceld with iteration of inade

Test3:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c}4 missing /dev/sd{e,f}4
-> filesize 1,4GB with 40745425 lines and canceling by e2fsck at the end
- errors see test2
- read error while reading next inode

Test4:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c,f,e,d}4
->filesize 874MB with 25412000 lines and break by e2fsck at the end
- try original superblock
- bad superblock or damaged partitiontable
- than lots of checksumm  invalid deskriptor of group
- at the end illegal block in inode to much invalid blocks in inode

Test5:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c}4 missing /dev/sd{e,d}4
-> filesize 1,6GB with 45673505 lines and canceling at the end by e2fsck

Test6:
mdadm --create --level 5 -n 6 --chunk=512 --assume-clean /dev/md2 /dev/sd{a,b,c,f,e}4 missing
- try original superblock
- bad superblock or damage partitiontable
- lots of checksumm error in group deskriptor
- ends with conflict in inode table with another filesystem block
-> filesize 542MB with 15727702 lines and cancelingat the end by e2fsck

Teset6 looks like the best one, but what do you think and perhaps what could i do else? Any further help?

Many thanks
Sunny


             reply	other threads:[~2013-02-08  9:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  9:17 Dragon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-10 21:27 Possible to rescue SW Raid5 with 2 missing Disks Dragon
2013-02-14 14:31 Dragon
2013-02-14 14:39 ` Mikael Abrahamsson
2013-02-14 15:01 Dragon
2013-02-14 17:09 ` Mikael Abrahamsson
2013-02-14 17:18   ` Dave Cundiff
2013-02-14 21:00 Dragon
2013-02-14 21:11 ` Robin Hill
2013-02-15  0:59 ` Dave Cundiff
2013-02-14 21:39 Dragon
2013-02-15  9:57 ` Mikael Abrahamsson
2013-02-15 11:14   ` Brad Campbell
2013-02-15 11:23     ` Mikael Abrahamsson
2013-02-15 12:12       ` Brad Campbell
2013-02-15 12:34         ` Mikael Abrahamsson
2013-02-15  9:46 Dragon
2013-02-15 12:59 Dragon
2013-02-15 14:51 ` Mikael Abrahamsson
2013-02-15 15:41 Dragon
2013-02-16  5:06 ` Mikael Abrahamsson
2013-02-18 12:13 Dragon
2013-02-19 15:19 Dragon
2013-02-19 17:48 ` Phil Turmel
2013-02-19 18:32   ` Roy Sigurd Karlsbakk
2013-02-19 20:36 Dragon
2013-02-20  7:44 Dragon
2013-02-20  8:06 ` Mikael Abrahamsson
2013-02-20  8:54 Dragon
2013-02-21 15:36 Dragon
2013-02-27  7:14 Dragon
2013-03-03 21:59 Dragon
2013-03-03 23:09 Dragon

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=20130208091700.256910@gmx.net \
    --to=sunghost@gmx.de \
    --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 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.