From: NeilBrown <neilb@suse.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: md raid behavior, bad sector uncorrectable read error
Date: Mon, 20 Aug 2012 08:19:35 +1000 [thread overview]
Message-ID: <20120820081935.24289755@notabene.brown> (raw)
In-Reply-To: <FEEB11B4-5CCB-49F4-8010-80CE03A49FA4@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Sun, 19 Aug 2012 12:12:38 -0600 Chris Murphy <lists@colorremedies.com>
wrote:
> On Aug 19, 2012, at 3:47 AM, Mikael Abrahamsson wrote:
> > If I remember correctly from what has been described here before, a read error will cause a re-write with information created from parity
>
> That's the thing I'd like to get a definitive answer one. If only it were easy to simulate bad sectors in VM's I could just test it!
If only it were easy to read the documentation, and if only the documentation
were sufficiently complete.....
% man 4 md
search for 'read error'
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-08-19 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 22:40 md raid behavior, bad sector uncorrectable read error Chris Murphy
2012-08-19 8:54 ` Albert Pauw
2012-08-19 18:12 ` Chris Murphy
2012-08-19 22:19 ` NeilBrown [this message]
2012-08-20 2:06 ` Chris Murphy
2012-08-20 12:36 ` Phil Turmel
2012-08-20 6:36 ` David Brown
2012-08-19 9:47 ` Mikael Abrahamsson
2012-08-19 10:39 ` Oliver Schinagl
-- strict thread matches above, loose matches on Subject: below --
2012-08-20 4:53 Richard Scobie
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=20120820081935.24289755@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.