All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Wols Lists <antlists@youngman.org.uk>,
	Brad Campbell <lists2009@fnarfbargle.com>,
	bobzer <bobzer@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: raid 5 crashed
Date: Wed, 1 Jun 2016 13:28:22 -0400	[thread overview]
Message-ID: <574F1B36.4030401@turmel.org> (raw)
In-Reply-To: <574F0258.5000108@youngman.org.uk>

On 06/01/2016 11:42 AM, Wols Lists wrote:

> Okay - so would this be better (a lot slower, possibly, but safe ...)
> 
> Use dd - so it DOES bomb on error! - and only replace the drive once
> you've got a clean read off it. With 2TB drives, that should work so
> long as they're not faulty. And if it's - JUST - a timeout issue,
> this'll work fine?

If there's errors, you'll never get a clean read.  (Short of the moon
and stars aligning for a near-miracle.)  ddrescue and similar replace
those errors with zeros to successfully retrieve less than 100% of your
data.

The whole point of keeping it in the array is to get the correct data
from the array's redundancy wherever the disk has unfixed read errors.
And with correct timeouts, to *FIX* that read error.  Please read *all*
of the links I posted on why and how this is.

Side note:  In these situations, you should *not* use overlays, as that
prevents the *FIX* part from happening.

Temporarily setting the timeouts for non-raid drives is a one-liner:

for x in /sys/block/*/device/timeout ; do echo 180 > $x ; done

Phil


      reply	other threads:[~2016-06-01 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 21:28 raid 5 crashed bobzer
2016-05-11 12:09 ` Mikael Abrahamsson
2016-05-11 13:15 ` Robin Hill
2016-05-26  3:06   ` bobzer
2016-05-27 19:19     ` bobzer
2016-05-30 15:01       ` bobzer
2016-05-30 19:04         ` Anthonys Lists
2016-05-30 22:00           ` bobzer
2016-05-31 13:45             ` Phil Turmel
2016-05-31 18:49               ` Wols Lists
2016-06-01  1:48                 ` Brad Campbell
2016-06-01  3:46                   ` Edward Kuns
2016-06-01  4:07                     ` Brad Campbell
2016-06-01  5:23                       ` Edward Kuns
2016-06-01  5:28                         ` Brad Campbell
2016-06-01 15:36                       ` Wols Lists
2016-06-01 23:15                         ` Brad Campbell
2016-06-02  5:52                           ` Mikael Abrahamsson
2016-06-02 14:01                           ` Wols Lists
2016-06-02 15:27                             ` Andreas Klauer
2016-06-03  1:05                             ` Brad Campbell
2016-06-03  7:52                               ` Mikael Abrahamsson
2016-06-03 15:27                                 ` bobzer
2016-06-03 16:31                                   ` Sarah Newman
2016-06-04  2:56                                     ` bobzer
2016-06-01 15:42                   ` Wols Lists
2016-06-01 17:28                     ` Phil Turmel [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=574F1B36.4030401@turmel.org \
    --to=philip@turmel.org \
    --cc=antlists@youngman.org.uk \
    --cc=bobzer@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=swmike@swm.pp.se \
    /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.