From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: RAID-6 with 3 missing disks
Date: Sat, 4 May 2013 18:08:04 +0200 [thread overview]
Message-ID: <20130504160804.GA2242@lazy.lzy> (raw)
Hi all,
I know this was probably already discussed, but
maybe I need some refresh.
I've a 10 HDDs RAID-6 which, due to mishap (disks
were disconnected accidentaly), has now 3 missing
devices and cannot be assembled.
The data should be OK, since no writes were occurring
during the accident, so putting them together again
should work.
As far as I know, one option is to create, with
"mdadm -C" the array again, giving the disks in
the proper order.
Since all HDDs are readable, I guess "mdadm -E"
should return the role of each device.
Is this correct for the creation order?
Second question is about the "Data Offset", since
this array was created with an older version of
"mdadm" and the data offset is very close to the
superblock.
As far as I know, new mdadm creates the data a
bit far aways.
Is there any way to specifiy the proper offset?
Finally, is there an alternative to "mdadm -C"
or it is the only option?
Forcing assembly does not work, but maybe there
is another way to tell mdadm to really assemby
the array, taking into account the superblock
information, which are all readable.
Thanks a lot in advance,
bye,
--
piergiorgio
next reply other threads:[~2013-05-04 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 16:08 Piergiorgio Sartor [this message]
2013-05-04 16:22 ` RAID-6 with 3 missing disks Rudy Zijlstra
2013-05-04 16:30 ` Piergiorgio Sartor
2013-05-05 2:58 ` NeilBrown
2013-05-05 8:43 ` Piergiorgio Sartor
2013-05-04 18:28 ` Piergiorgio Sartor
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=20130504160804.GA2242@lazy.lzy \
--to=piergiorgio.sartor@nexgo.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 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).