From: Mike Power <mpower@dodtsair.com>
To: linux-raid@vger.kernel.org
Subject: mdadm and disk failures
Date: Wed, 15 Jun 2011 20:37:31 -0700 [thread overview]
Message-ID: <4DF97A7B.1070901@dodtsair.com> (raw)
I was looking around the wiki and I could not find the answer.
I wanted to know if the raid system will recover bad blocks lost on the
one device when the copies of those blocks are available on another.
From what I understand when a hard drive loses a block it replaces it
with another block but it can not recover the data. At this point I do
not know what the raid system does. At one point in the past my
understanding is, the raid system did nothing. If it read from the disk
that had the block it gets garbage for data. Conceptually the raid
system could read the data from one disk and write it to the copy on the
other and restore the data.
Is the raid system capable of recovering and restoring bad blocks?
Mike Power
next reply other threads:[~2011-06-16 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 3:37 Mike Power [this message]
2011-06-16 4:39 ` mdadm and disk failures Brad Campbell
2011-06-16 4:59 ` Roman Mamedov
2011-06-16 5:29 ` Mikael Abrahamsson
2011-06-16 15:34 ` Mike Power
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=4DF97A7B.1070901@dodtsair.com \
--to=mpower@dodtsair.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;
as well as URLs for NNTP newsgroup(s).