From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Another Sillyname <anothersname@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
Date: Mon, 21 Sep 2015 09:12:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1509210909380.8750@uplift.swm.pp.se> (raw)
In-Reply-To: <CAOS+5GHtJAYdHEHnvb+Akfc+jkh5es8cb8z50YQwB23rnk+_Sw@mail.gmail.com>
On Mon, 21 Sep 2015, Another Sillyname wrote:
> Thanks for the help and advice....and most of all the confirmation my
> approach was the correct one.
It would be helpful if you posted the dmesg output from what you did. So
while this approach is ok, so you stated, you're vulnerable to read errors
on the remaining drives.
It's possible a newer mdadm would have --assemble --force in the two last
drives as well. You have an internal bitmap, which should have meant that
you shouldn't have had to do a full resync.
So what happened to you isn't optimal and it would be helpful to
understand what kernel version, mdadm version you used, and what the
output from your steps were.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2015-09-21 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 18:33 Failed Raid6 Array.....want some guidance before attempting restart Another Sillyname
2015-09-20 5:34 ` Mikael Abrahamsson
[not found] ` <CAOS+5GEcpOV6dkkGYHjkA3ah88MXqyJ0AFS7T--qaCc-Z1-=uw@mail.gmail.com>
2015-09-20 9:19 ` Fwd: " Another Sillyname
2015-09-20 9:54 ` Mikael Abrahamsson
2015-09-21 1:32 ` Another Sillyname
2015-09-21 1:59 ` Another Sillyname
2015-09-21 7:12 ` Mikael Abrahamsson [this message]
2015-09-21 7:57 ` Another Sillyname
2015-09-21 7:57 ` Alexander Afonyashin
2015-09-21 8:05 ` Another Sillyname
2015-09-21 8:09 ` Another Sillyname
2015-09-22 9:33 ` Another Sillyname
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=alpine.DEB.2.02.1509210909380.8750@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=anothersname@googlemail.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