All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ole Olsen <gnu@gmx.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: reshape raid5 to raid6
Date: Wed, 24 Jun 2009 15:32:45 +0200	[thread overview]
Message-ID: <20090624133245.GA2828@rlogin.dk> (raw)
In-Reply-To: <972c997a386db1106868b3dc6b29ee21.squirrel@neil.brown.name>

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

Hello I just compiled the 2.6.30 kernel from kernel.org
I was running 29.3 and 2.6.7.2 mdadm (Nov 08) Debian lenny, but kernel from
kernel.org.

I added the new device with echoing into /sys as you described

mfs:/home/michael# mdadm --zero-superblock /dev/sdc (It was an old disk from
the raid that was taken out long ago and not used - array was not degraded,
so I can just zero it)

mfs:/home/michael# mdadm --add /dev/md0 /dev/sdc

mfs:/home/michael# cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] 
md0 : active raid6 sdc[10] sdi[0] sda[8] sdj[7] sdb[6] sde[5] sdg[4] sdd[3]
sdh[2] sdf[1]
      11721107968 blocks level 6, 64k chunk, algorithm 18 [10/9] [UUUUUUUUU_]
            [>....................]  recovery =  0.9% (14365824/1465138496)
    finish=414.1min speed=58382K/sec

the raid6 seems to be working, at least proc says so.

after stopping my reads and writes to the disk the reshape went 
from approximately 1000kB/s to 55000kB/s (i think i was only reading a bit from it)

440 minutes till reshape, so seems to go just fine.

I will try to re-stripe (and of course backup data first) with the new mdadm 
when it comes out, looking forward to it, thanks

/Michael Ole Olsen


NeilBrown schrieb am Wednesday, den 24. June 2009:

> On Wed, June 24, 2009 8:27 pm, Michael Ole Olsen wrote:
> > Is it possible to reshape my /dev/md0 raid5 into raid6?
> 
> If you are are using Linux 2.6.30, then you can
> 
>   echo raid6 > /sys/block/md0/md/level
> 
> and it will instantly be sort-of-raid6.
> It is exactly like raid6 except that the Q blocks are all one
> the one drive, and drive that previously didn't exist.
> If you have a spare, it will start building the Q blocks
> on that drive and when it finishes you will have true raid6
> redundancy, though possibly a little less than raid6 performance,
> as a real raid6 has the Q block distributed.
> 
> When mdadm-3.1 is released, you will be able to tell the raid6
> to re-stripe with a more traditional layout.  This will take quite
> a while, but you can continue to use the array (though a bit more
> slowly) will it progresses.
> Of course you don't need to do that step if you don't want to.
> 
> 
> 
> >
> > I found the following recipe in the docs:
> > mdadm --create /dev/md0 -l6 -n4 /dev/sdb1 /dev/sdc1 /dev/sdd1 missing
> >
> > I have 9 disks in my raid5, would i then do:
> > [1] mdadm --create /dev/md0 -l6 -n10 /dev/sda /dev/sdb ... missing
> 
> If you did this, an the drives contained raid5 data, then that data
> would not be available on /dev/md0.
> 
> NeilBrown
> 
> 
> >
> > i.e. only the first 9 drives and then hot add a new device to get it to
> > reshape and add the extra parity to all drives?
> >
> > mdadm --add /dev/md0 /dev/sdk ?
> >
> > I would guess  command [1] would give problems as md0 is an active array
> > will it work if i --stop the array first so that i can reshape to raid6?
> >
> > I couldn't really find much information on this, some say it is impossible
> > without recreating the array? (So i ask here first before i try, as I dont
> > want to risk my data, even though I have backups of the important
> > data)
> >
> > Any advice would be nice
> >
> > /Michael Ole Olsen
> >
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2009-06-24 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 10:27 reshape raid5 to raid6 Michael Ole Olsen
2009-06-24 11:20 ` NeilBrown
     [not found]   ` <aebf5d970906240515y6c616250lca1cedea32927b00@mail.gmail.com>
2009-06-24 12:17     ` Beolach
2009-07-09  8:36       ` Mikael Abrahamsson
2009-07-09  9:35         ` NeilBrown
2009-06-24 13:32   ` Michael Ole Olsen [this message]
2009-06-24 16:10   ` Billy Crook
2009-06-26  2:00     ` Neil Brown
2009-07-15  3:29       ` Michael Ole Olsen
2009-07-15  3:58         ` NeilBrown

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=20090624133245.GA2828@rlogin.dk \
    --to=gnu@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.