linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can't reshape RAID1 to RAID5 due to chunk size
Date: Wed, 19 Sep 2012 13:46:01 +0600	[thread overview]
Message-ID: <20120919134601.0671d75f@natsu> (raw)
In-Reply-To: <20120919162058.3101366d@notabene.brown>

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

On Wed, 19 Sep 2012 16:20:58 +1000
NeilBrown <neilb@suse.de> wrote:

> What you need to do is:
>   - make sure the filesystem in /dev/md1 doesn't use the last 3k (it probably 
>     uses a 4K block size, so cannot use that last bit
>   - resize the array down to 488372860K  (mdadm -G /dev/md0 --size 488372860)
>   - convert to a 2-device RAID5 with a 4K chunk size:
>       mdadm -G /dev/md1 -c 4K -l5 -n2
>   - convert to a 3-device RAID5 with a 64K chunk size:
>       mdadm -G /dev/md1 -c 64k -n3
> 
> NeilBrown

Thanks, Neil.

I have since finished this migration in another way, luckily I had some spare
drives lying around, so had an option to create a separate RAID5 from scratch
and move over & replace the drives one by one.

By the way the "want_replacement" feature is totally awesome, thanks to it at
no point in my operations I was left without redundancy (after all a N-disk
degraded RAID5 reliability-wise is like a RAID0 of N disks, and that's
something I wanted to avoid having even for a short period).

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

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

      reply	other threads:[~2012-09-19  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  4:59 Can't reshape RAID1 to RAID5 due to chunk size Roman Mamedov
2012-09-19  6:20 ` NeilBrown
2012-09-19  7:46   ` Roman Mamedov [this message]

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=20120919134601.0671d75f@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).