From: "P. Gautschi" <linuxlist@gautschi.net>
To: Phil Turmel <philip@turmel.org>
Cc: Vince <stuff@hagenhuegel.de>, linux-raid@vger.kernel.org
Subject: Re: Raid5 drive fail during grow and no backup
Date: Fri, 07 Nov 2014 17:06:19 +0100 [thread overview]
Message-ID: <545CEDFB.6060806@gautschi.net> (raw)
In-Reply-To: <5458FC2A.1050308@turmel.org>
> This is a problem you haven't solved yet, I think. The raid array should have fixed this bad sector for you without kicking the drive out. The scenario is common with "green" drives and/or consumer-grade drives in general.
> ...
> Then you can set up your array to properly correct bad sectors, and set your system to look for bad sectors on
> a regular basis.
What is the behavior of mdadm when a disk reports a read error?
- reconstruct the data, deliver it to the fs and otherwise ignore it?
- set the disk to fail?
- reconstruct the data, rewrite the failed data and continue with any action?
- rewrite the failed data and reread it (bypassing the cache on the HD)?
Do read operation always read the parity too in order to detect problems early
before a sector on a other disks fails?
Can the behavior be configured in any way? I found no documentation regarding this.
Patrick
next prev parent reply other threads:[~2014-11-07 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 13:34 Raid5 drive fail during grow and no backup Vince
2014-11-02 3:22 ` Phil Turmel
2014-11-03 14:45 ` Vince
2014-11-04 16:17 ` Phil Turmel
2014-11-05 19:03 ` Vince
2014-11-06 17:12 ` Vince
2014-11-07 13:36 ` Phil Turmel
2014-11-07 16:07 ` P. Gautschi
2014-11-07 16:06 ` P. Gautschi [this message]
2014-11-08 3:36 ` Phil Turmel
2014-11-10 3:20 ` Jason Keltz
2014-12-04 19:29 ` Phillip Susi
2014-12-04 20:02 ` Phil Turmel
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=545CEDFB.6060806@gautschi.net \
--to=linuxlist@gautschi.net \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=stuff@hagenhuegel.de \
/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.