linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Boyan Alexiev <alexiev@resonance.bg>
Cc: linux-raid@vger.kernel.org
Subject: Re: Backup file size when migrating from raid5 to raid6?
Date: Thu, 18 Jul 2013 06:51:59 +1000	[thread overview]
Message-ID: <20130718065159.0a40207e@notabene.brown> (raw)
In-Reply-To: <loom.20130717T145156-76@post.gmane.org>

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

On Wed, 17 Jul 2013 13:01:15 +0000 (UTC) Boyan Alexiev <alexiev@resonance.bg>
wrote:

> If You have array with 9 devices and add another one You may at same time
> grow array and change raid level. In this case You not need backup file.
> Please try this:
> mdadm --grow /dev/md0 --raid-devices=10 --level=6 
> 

You can only skip the backup file if you  are increasing the number of *data*
devices.  I don't think your example does that.

(However with mdadm-3.3 this problem goes away if you have a new enough
kernel).

NeilBrown

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

      reply	other threads:[~2013-07-17 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH-e9vLTY2eo0p3ud5FaWNe_2f8hej0aitFuu8K0M1RZdObiXQ@mail.gmail.com>
2012-05-06 10:17 ` Backup file size when migrating from raid5 to raid6? Garðar Arnarsson
2012-05-06 11:00   ` NeilBrown
     [not found]     ` <CAH-e9vJkrv2R-HTR7JfHwZK1sbYQ3fduGbtxEwtor4gtyd6PKQ@mail.gmail.com>
2012-05-07  0:35       ` Garðar Arnarsson
2012-05-07  0:54       ` NeilBrown
2012-08-16 23:28         ` Thomas Fjellstrom
2012-08-17  0:39           ` NeilBrown
2012-08-17  0:45             ` Thomas Fjellstrom
2012-08-17  0:52           ` John Robinson
2013-07-17 13:01   ` Boyan Alexiev
2013-07-17 20:51     ` NeilBrown [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=20130718065159.0a40207e@notabene.brown \
    --to=neilb@suse.de \
    --cc=alexiev@resonance.bg \
    --cc=linux-raid@vger.kernel.org \
    /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).