Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Maarten <maarten@ultratux.net>, linux-raid@vger.kernel.org
Subject: Re: 3-disk fail on raid-6, examining my options...
Date: Tue, 18 Jul 2017 21:20:02 +0100	[thread overview]
Message-ID: <596E6D72.8050108@youngman.org.uk> (raw)
In-Reply-To: <07b77b80-4bee-3820-6a0d-3323ef06a3f3@ultratux.net>

On 18/07/17 18:20, Maarten wrote:
> Now from what I've gathered over the years and from earlier incidents, I
> have now 1 (one) chance left to rescue data off this array; by hopefully
> cloning the bad 3rd-failed drive with the aid of dd_rescue and
> re-assembling --force the fully-degraded array. (Only IF that drive is
> still responsive and can be cloned)

If it clones successfully, great. If it clones, but with badblocks, I
keep on asking - is there any way we can work together to turn
dd-rescue's log into a utility that will flag failed blocks as "unreadable"?

This project is mentioned on the wiki, the idea being that you can tell
the hard drive to return a read error if the computer tries to access
certain blocks. This "fake" read error means that we can then use a
partially copied disk to rebuild an array knowing that we will get an
error rather than silent corruption if we try and access the faulty block.

At least then, we know what is damaged rather than trying to
integrity-check an entire disk in the hope that we'll detect the corruption.

Cheers,
Wol

  reply	other threads:[~2017-07-18 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 17:20 3-disk fail on raid-6, examining my options Maarten
2017-07-18 20:20 ` Wols Lists [this message]
2017-07-18 20:25   ` Wakko Warner
2017-07-18 21:29     ` Maarten
2017-07-19 11:51     ` Wols Lists
2017-07-19 17:09       ` Wakko Warner

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=596E6D72.8050108@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=maarten@ultratux.net \
    /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