From: Phillip Susi <psusi@ubuntu.com>
To: Phil Turmel <philip@turmel.org>, "P. Gautschi" <linuxlist@gautschi.net>
Cc: Vince <stuff@hagenhuegel.de>, linux-raid@vger.kernel.org
Subject: Re: Raid5 drive fail during grow and no backup
Date: Thu, 04 Dec 2014 14:29:03 -0500 [thread overview]
Message-ID: <5480B5FF.5050407@ubuntu.com> (raw)
In-Reply-To: <545D8FBA.9090701@turmel.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/7/2014 10:36 PM, Phil Turmel wrote:
> However, if the device with the bad sector is trying to recover
> longer than the linux low level driver's timeout, bad things^TM
> happen. Specifically, the driver resets the SATA (or SCSI)
> connection and attempts to reconnect. During this brief time, it
> will not accept further I/O, so the write back of the reconstructed
> data fails. Then the device has experienced a *write* error, so MD
> fails the drive. This is the out-of-the-box behavior of
> consumer-grade drives in raid arrays.
What? During the recovery action ( reset and retry ), a write being
issued to the drive should just sit in the request queue until after
the drive finishes being reset; it should not just be failed outright.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUgLX+AAoJENRVrw2cjl5RHb4H+wWzuTFekQMwIoX7Vov5QjLh
XyEmgbwqgtdcnsbQqtnNiQK0k8KVxQDW3xzWkB30PkOjWMfldES3dRjFXuNbZ0r1
FnJeIYbChFBnfJLp/BqHHOnL5YHD81HvENJ4M/OW6t9SpSiFuOieFe7WTEwHoh5t
t9v/J0+x84CQu1q/AF7FRMkLE1fYhZieAMLTyKhbo5TmMm5XSP8eXumMCz+PXmvV
tVN6rYejSozl1wfwa0l4N9jwkyYWLgbzFRIR7PuQNacywFyLhg0WtIPnqjNV6YuL
rAl5VBFbHEn6BwklgxDWkzSIuOIt2ce6KIE0JZtqTGlDajhSUM+ojTPALLFcmLE=
=4mKS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-04 19:29 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
2014-11-08 3:36 ` Phil Turmel
2014-11-10 3:20 ` Jason Keltz
2014-12-04 19:29 ` Phillip Susi [this message]
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=5480B5FF.5050407@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-raid@vger.kernel.org \
--cc=linuxlist@gautschi.net \
--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 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).