linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: den Hoog <speedyden@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
Date: Mon, 20 Jan 2014 17:16:45 +1100	[thread overview]
Message-ID: <20140120171645.591b17fc@notabene.brown> (raw)
In-Reply-To: <CANgodhDZnogCmXDLz75Hidv=HcYoaoj=1thKTqt8htP8gx3CSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Thu, 16 Jan 2014 22:03:00 +0100 den Hoog <speedyden@gmail.com> wrote:

> Hi Neil
> 
> can you try to make 'missing' working for imsm?
> 
> probably not on the short list of things to do, but if you are willing
> to help me out, I'll appreciate it much!

Hi Dennis,

it seems that "missing" already works with IMSM.  I thought I remembered that
it didn't, but I was wrong.

So you should be able to create the raid0 using the first parts of the
devices, then create the RAID5.
When creating the RAID5, list the devices that should  make up the RAID5 in
the correct order.
So something like:

 mdadm -C /dev/md/imsm -e imsm -n 4 /dev/sd[bcde]
 mdadm -C /dev/md0 -l0 -n4 -c 128k -z 512G /dev/md/imsm
 mdadm -C /dev/md1 -l5 -n4 -c 128k missing /dev/sdc /dev/sdd /dev/sde

Then /dev/md1 should be your RAID5 array.

You should double-check the above command to make sure you agree with ever
part, and ask if there is anything that doesn't seem right.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-01-20  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 19:45 looking for advice on raid0+raid5 array recovery with mdadm and sector offset den Hoog
2014-01-06  1:41 ` NeilBrown
2014-01-06  6:53   ` den Hoog
2014-01-07 21:43     ` den Hoog
2014-01-16 21:03       ` den Hoog
2014-01-20  6:16         ` NeilBrown [this message]
2014-01-20 21:43           ` den Hoog
2014-01-20 22:11             ` NeilBrown
2014-01-20 22:51               ` NeilBrown
2014-01-24 23:13                 ` den Hoog

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=20140120171645.591b17fc@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=speedyden@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).