Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Wols Lists <antlists@youngman.org.uk>
Cc: 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 16:25:50 -0400	[thread overview]
Message-ID: <20170718202550.GA2533@animx.eu.org> (raw)
In-Reply-To: <596E6D72.8050108@youngman.org.uk>

Wols Lists wrote:
> 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"?

I wrote a shell script that will output a device mapper table to do this. 
It will do either zero or error targets for failed blocks.  It's not
automatic and does require a block device (loop for files).  I've used this
several times at work and works for me.

I'm not sure if this is what you're talking about or not, but if you want
the script, I'll post it.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.

  reply	other threads:[~2017-07-18 20:25 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
2017-07-18 20:25   ` Wakko Warner [this message]
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=20170718202550.GA2533@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=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