From: Wakko Warner <wakko@animx.eu.org>
To: linux-raid@vger.kernel.org
Subject: mdadm and the list appreciation
Date: Tue, 10 Dec 2013 20:06:34 -0500 [thread overview]
Message-ID: <20131211010634.GB30462@animx.eu.org> (raw)
I've not posted much on the list, but I have read the help that the regulars
have given to others.
Today, I had 6 drive drop at one time from my array. I know why they did
and that has been corrected.
I yanked all the drives from the das box, shutdown all the volumes and then
the array itself. Then one by one plugged each drive back in waiting for
the kernel to see the drive before going to the next one.
As expected, mdadm -A /dev/mdX <drive list>
didn't work, stated 2 devices were not enough.
I added --force to that and it came up just fine. I had some large files
that I could sum to verify that it assembled properly. They checked out OK.
I'm running a check on the array and so far no mismatch count.
Fortunately, nothing was in use at the time this happened.
I'm posting this just to let you guys know how much your help of others
helped me this time. Atleast I didn't resort to recreating the array again!
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
reply other threads:[~2013-12-11 1:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131211010634.GB30462@animx.eu.org \
--to=wakko@animx.eu.org \
--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).