From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid-owner@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: RAID-6 with 3 missing disks
Date: Sat, 4 May 2013 18:30:06 +0200 [thread overview]
Message-ID: <20130504163006.GA3395@lazy.lzy> (raw)
In-Reply-To: <14872633-1367684555-cardhu_decombobulator_blackberry.rim.net-102434637-@b3.c7.bise7.blackberry>
Hi Rudy,
thanks for the answer, but as mentioned at the end,
"--force" assemby does not work.
Reason is, 7 disks complains 3 are missing and the
3 missing are assembed, since their superblock does
not report errors.
Of course, 3 disks are not enough to assembly the
array, forced or not.
bye,
pg
On Sat, May 04, 2013 at 04:22:39PM +0000, Rudy Zijlstra wrote:
> Hi
>
> I would start with mdadm assemble --force
>
> Do not use create unless all else has failed
>
> Cheers
>
> Rudy
> ---
> Verstuurd met mijn BlackBerry van Vodafone
>
> -----Original Message-----
> From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
> Sender: linux-raid-owner@vger.kernel.org
> Date: Sat, 4 May 2013 18:08:04
> To: <linux-raid@vger.kernel.org>
> Subject: RAID-6 with 3 missing disks
>
> 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
> --
> 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
--
piergiorgio
next prev parent reply other threads:[~2013-05-04 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 16:08 RAID-6 with 3 missing disks Piergiorgio Sartor
2013-05-04 16:22 ` Rudy Zijlstra
2013-05-04 16:30 ` Piergiorgio Sartor [this message]
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=20130504163006.GA3395@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid-owner@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rudy@grumpydevil.homelinux.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).