From: "John Stoffel" <john@stoffel.org>
To: Alberto Morell <amp4tj@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: Unable to re-assemble a raid 10 after it has FAILED.
Date: Tue, 10 Jun 2014 16:28:48 -0400 [thread overview]
Message-ID: <21399.27264.433526.990888@quad.stoffel.home> (raw)
In-Reply-To: <CAEp9EKg462T+7E35RnarP6y41wGgNv3R_jAXEhxiLBg_vukW3g@mail.gmail.com>
>>>>> "Alberto" == Alberto Morell <amp4tj@gmail.com> writes:
Alberto> I have a raid 10 devices with 4 components. I make the raid
Alberto> fails, by making two components fail (using "mdadm
Alberto> --set-faulty <device>"). When I add the two devices back,
Alberto> they are added as spare devices. Then, I can get the raid
Alberto> active again only creating the raid again using "mdadm
Alberto> --create --assume-clean...". Re-assembling the device does
Alberto> not work with error message:
Alberto> mdadm: failed to RUN_ARRAY /dev/md/hdd: Input/output error
Alberto> mdadm: Not enough devices to start the array.
Alberto> I am trying to automate the raid configuration and the "mdadm --create
Alberto> ..." option is not convenient as I would have to know all the creation
Alberto> parameters.
Alberto> Below is the command sequence.
Alberto> Thanks is advance,
Alberto> Alberto Morell.
Alberto> [root@os2 raid_tools]# mdadm --version
Alberto> mdadm - v3.2.6 - 25th October 2012
Alberto> [root@os2 ~]# mdadm --create /dev/md/hdd --metadata=1.0 --auto=md --name=hdd \
Alberto> --chunk=256 --bitmap=internal --bitmap-chunk=65536 --level=raid10 --run \
Alberto> --raid-devices=4 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
Alberto> [root@os2 ~]# mdadm --set-faulty /dev/md/hdd /dev/sde1
Alberto> mdadm: set /dev/sde1 faulty in /dev/md/hdd
Alberto> [root@os2 ~]# mdadm --set-faulty /dev/md/hdd /dev/sdf1
Alberto> mdadm: set /dev/sdf1 faulty in /dev/md/hdd
You do realize that you killed the last two drives in the array,
right? sdc1 and sdd1 are mirrored with each other, and sde1 and sdf1
are mirrored to each other. When you kill those two drives, the
entire array *must* go offline to try and save data. It's not likely,
since the filesystem spread across all four drives is probably toast
now...
At least that's how I think the RAID10 works be default. If you use
one of the other layouts, you might have lucked out by not killing
both halves of a raid pair.
John
prev parent reply other threads:[~2014-06-10 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEp9EKjgt1RTkYzhSX-UQN2-WhV3iCKPr_DTnHN_KmorvFNsvg@mail.gmail.com>
2014-06-10 11:04 ` Fwd: Unable to re-assemble a raid 10 after it has FAILED Alberto Morell
2014-06-10 11:30 ` NeilBrown
2014-06-11 7:24 ` Alberto Morell
2014-06-10 20:28 ` John Stoffel [this message]
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=21399.27264.433526.990888@quad.stoffel.home \
--to=john@stoffel.org \
--cc=amp4tj@gmail.com \
--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