All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>, Martin Bosner <martin@bosner.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: assistance recovering failed raid6 array
Date: Mon, 20 Feb 2017 20:45:09 +0000	[thread overview]
Message-ID: <58AB5555.5070504@youngman.org.uk> (raw)
In-Reply-To: <fcf34399-2f7a-f444-bff7-512ae29d2e7b@turmel.org>

On 20/02/17 19:16, Phil Turmel wrote:
> For every stripe in the array, you need 34 devices of 36 to be
> readable.  Any time you fall back on ddrescue to make one of those
> 34, you are ensuring that some data is lost.  But yes, that would
> otherwise work.  The 2/3 recovered disk is only useful in this (use
> ddrescue to get as much of the missing disk as possible).

I keep on asking :-)

But there's a request on the linux wiki program for someone to write a
utility program that takes a ddrescue log and flags the duff sectors as
"soft unreadable". That would mean that if you can recover 35 drives,
provided no stripe has lost two sectors across two drives, you wouldn't
lose any data.

If you want to try and write that utility? Or if you want to email me a
ddrescue log with a bunch of failed sectors, I'll have a go at writing
it myself :-)

Cheers,
Wol

  parent reply	other threads:[~2017-02-20 20:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20  1:49 assistance recovering failed raid6 array Martin Bosner
2017-02-20 15:39 ` Phil Turmel
     [not found]   ` <E18A7C79-09E0-4361-9F89-68AE1E6FCBF6@bosner.de>
2017-02-20 17:36     ` Phil Turmel
2017-02-20 17:48       ` Martin Bosner
2017-02-20 18:11         ` Phil Turmel
2017-02-20 18:27           ` Martin Bosner
2017-02-20 19:01             ` Wols Lists
2017-02-20 19:11               ` Martin Bosner
2017-02-20 19:16             ` Phil Turmel
2017-02-20 19:31               ` Martin Bosner
2017-02-20 21:30                 ` Phil Turmel
2017-02-20 20:45               ` Wols Lists [this message]
2017-02-20 21:21                 ` Phil Turmel
2017-02-21  2:03                   ` Brad Campbell
2017-02-20 17:50       ` Roman Mamedov
2017-02-20 18:13         ` Martin Bosner

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=58AB5555.5070504@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin@bosner.de \
    --cc=philip@turmel.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 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.