From: NeilBrown <neilb@suse.com>
To: Nate Clark <nate@neworld.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: I/O error reading from raid 1 device but not slave devices
Date: Wed, 1 Jul 2015 10:53:42 +1000 [thread overview]
Message-ID: <20150701105342.4761c795@noble> (raw)
In-Reply-To: <CAG2YfWOn5_9KAK+qFY3XBBrh2L2HuxDCoc_6kzEEV8diyeG3Wg@mail.gmail.com>
On Tue, 30 Jun 2015 10:46:38 -0400 Nate Clark <nate@neworld.us> wrote:
> On Mon, Jun 29, 2015 at 5:35 PM, Nate Clark <nate@neworld.us> wrote:
> > Hello,
> >
> > I have encountered a strange error while reading from a raid 1 device.
> > If I read from the md device I encounter an I/O error, however if I
> > read from the underlying devices there is no issue.
>
> It appears both drives in the array have identical bad blocks list. I
> am not sure why any blocks were marked bad since I don't see any drive
> I/O errors in the logs and the smart output from each drive shows they
> are healthy.
That was my guess, but you confirmed before I got around to posting :-)
One way you could get bad blocks on perfectly healthy drives is if you
previously had an unhealthy drive.
Imagine a degraded RAID1 with a drive that has a couple of bad blocks.
You add a spare, it recovers but as it cannot read the bad blocks, it
adds them to the badblock list on the new device.
Then you remove the sick device, add a brand new one, and rebuild it -
from the first spare you added.
It will get the bad blocks "copied" onto it as well.
The blocks will stay 'bad' until something is written to them. Then
they will become good.
NeilBrown
prev parent reply other threads:[~2015-07-01 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 21:35 I/O error reading from raid 1 device but not slave devices Nate Clark
2015-06-30 14:46 ` Nate Clark
2015-07-01 0:53 ` 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=20150701105342.4761c795@noble \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=nate@neworld.us \
/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).