From: NeilBrown <neilb@suse.de>
To: Andy Smith <andy@strugglers.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can extremely high load cause disks to be kicked?
Date: Mon, 4 Jun 2012 14:13:12 +1000 [thread overview]
Message-ID: <20120604141312.175ec480@notabene.brown> (raw)
In-Reply-To: <20120531083158.GE3867@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On Thu, 31 May 2012 08:31:58 +0000 Andy Smith <andy@strugglers.net> wrote:
> Now, is this sort of behaviour expected when under incredible load?
> Or is it indicative of a bug somewhere in kernel, mpt driver, or
> even flaky SAS controller/disks?
This sort of high load would not affect md, except to slow it down.
My guess is that the real bug is in the mpt driver, but as I know nothing
about the mpt driver, you should treat that guess with a few kilos of NaCl.
>
> Root cause of failure aside, could I have made recovery easier? Was
> there a better way than --create --assume-clean?
The mis-step was to try to add the devices back to the array. A newer
mdadm would refuse to let you do this because of the destructive effect.
The correct step would have been to stop the array and re-assemble it,
with --force.
Once you had turned the devices to spares with --add, --create --assume-clean
was the correct fix.
>
> If I had done a --create with sdc5 (the device that stayed in the
> array) and the other device with the closest event count, plus two
> "missing", could I have expected less corruption when on 'repair'?
Possibly. You certainly wouldn't expect more.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-06-04 4:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 8:31 Can extremely high load cause disks to be kicked? Andy Smith
2012-06-01 1:31 ` Stan Hoeppner
2012-06-01 3:15 ` Igor M Podlesny
2012-06-01 14:12 ` Stan Hoeppner
2012-06-01 15:19 ` Igor M Podlesny
2012-06-02 4:45 ` Stan Hoeppner
2012-06-02 7:57 ` Igor M Podlesny
2012-06-02 9:16 ` Stan Hoeppner
2012-06-01 19:25 ` Andy Smith
2012-06-02 5:47 ` Stan Hoeppner
2012-06-03 3:30 ` Andy Smith
2012-06-03 4:05 ` Igor M Podlesny
2012-06-03 22:05 ` Andy Smith
2012-06-04 1:55 ` Stan Hoeppner
2012-06-04 9:06 ` Igor M Podlesny
2012-06-03 6:49 ` Stan Hoeppner
2012-06-04 0:02 ` Andy Smith
2012-06-04 6:58 ` Stan Hoeppner
2012-06-04 4:13 ` NeilBrown [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=20120604141312.175ec480@notabene.brown \
--to=neilb@suse.de \
--cc=andy@strugglers.net \
--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).