linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Marek <mlf.conv@gmail.com>, Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Fwd: manually destriping a 4 drive raid5 with one missing drive
Date: Fri, 23 Oct 2015 13:49:39 -0400	[thread overview]
Message-ID: <562A7333.9010702@turmel.org> (raw)
In-Reply-To: <CA+sqOsY1Q4e3vNy4rmqjndsOStSGOg4JpqWBm4TTEvRdOmTkbQ@mail.gmail.com>

On 10/23/2015 12:20 PM, Marek wrote:
> Not sure if it's destrip or destripe but it's basically like puzzle
> you take a block from each drive according to the layout you are using
> e.g. Left symmetric and then write it down in that order computing
> missing blocks from parity blocks - this way you would write an image
> which you can mount without using mdadm. Data restoration companies
> are using this technique.

No special tool required.  Obtain a new drive big enough to hold your
entire array and 'dd' from /dev/mdX to your new drive.

{ BTW: convention on kernel.org is to reply-to-all, trim unnecessary
context, and either bottom post or interleave your reply. }

Phil

  reply	other threads:[~2015-10-23 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 18:58 manually destriping a 4 drive raid5 with one missing drive Marek
2015-10-17 22:54 ` Neil Brown
     [not found]   ` <CA+sqOsZJbvyAW6=CSG5EikhmDPt+Onjpm+VvBNPMKFmVi-ZQ8g@mail.gmail.com>
2015-10-23  9:26     ` Fwd: " Marek
2015-10-23 11:50       ` Alexander Afonyashin
2015-10-23 15:53       ` Piergiorgio Sartor
     [not found]         ` <CA+sqOsYBbOwn5tJfygAR0MDCQPpd4w61XPGBLv8Mme8cT_HL8A@mail.gmail.com>
2015-10-23 16:20           ` Fwd: " Marek
2015-10-23 17:49             ` Phil Turmel [this message]
2015-10-23 20:46               ` Marek
2015-10-23 21:30                 ` Dragan Milivojević
2015-10-25 22:47                 ` 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=562A7333.9010702@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mlf.conv@gmail.com \
    /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).