From: Piotr Klimek <piotr@klimek.net.pl>
To: linux-raid@vger.kernel.org
Subject: RAID6 reshape integer problem
Date: Fri, 3 Jan 2014 09:30:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20140103T101338-556@post.gmane.org> (raw)
Hello,
I was trying to migrate from 5x3TB RAID5 to 6x3TB RAID6 with this command:
$ mdadm --grow /dev/md1 --level=6 --raid-devices=6 --
backup=/home/archiwum/r6.bak
After couple of days reshape stalled on 2147483648 block. I have found that
this is a bug in mdadm. 2147483648 is max integer on 32 bit system. For now
situation looks like this:
$ uname -a
Linux backuper 2.6.32-5-686-bigmem #1 SMP Mon Sep 23 23:38:27 UTC 2013 i686
GNU/Linux
$ mdadm --version
mdadm - v3.1.4 - 31st August 2010
$ cat /proc/mdstat
md1 : active raid6 sdi1[6] sdj1[0] sdk1[5] sdc1[4] sdf1[3] sdh1[1]
11721054208 blocks super 1.2 level 6, 512k chunk, algorithm 18 [6/5]
[UUUUU_]
[==============>......] reshape = 73.2% (2147483648/2930263552)
finish=18031577.4min speed=0K/sec
$ mdadm --detail /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Mon Nov 25 11:41:34 2013
Raid Level : raid6
Array Size : 11721054208 (11178.07 GiB 12002.36 GB)
Used Dev Size : 2930263552 (2794.52 GiB 3000.59 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Fri Jan 3 10:26:20 2014
State : clean, degraded, recovering
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric-6
Chunk Size : 512K
Reshape Status : 73% complete
New Layout : left-symmetric
Name : backuper:1 (local to host backuper)
UUID : 5fb40412:f3447bf7:f654d5f1:1bef1e1c
Events : 4553396
Number Major Minor RaidDevice State
0 8 145 0 active sync /dev/sdj1
1 8 113 1 active sync /dev/sdh1
3 8 81 2 active sync /dev/sdf1
4 8 33 3 active sync /dev/sdc1
5 8 161 4 active sync /dev/sdk1
6 8 129 5 spare rebuilding /dev/sdi1
What should I do now? Its a production system, of course I have a backups
but I would like to avoid recovering 8TB data from backups. My idea is to
cancel reshape, and then do it again with bigger chunk, or upgrade
mdadm/kernel.
Thanks in advance for your help.
next reply other threads:[~2014-01-03 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 9:30 Piotr Klimek [this message]
2014-01-03 12:56 ` RAID6 reshape integer problem Phil Turmel
2014-01-03 13:43 ` Piotr Klimek
[not found] ` <CAM8eUy0=YbC68vesaLPSp0RhL_2c8byVyROMGv2DdQ2_JSjYrg@mail.gmail.com>
2014-01-03 17:07 ` Phil Turmel
2014-01-08 11:19 ` Piotr Klimek
2014-01-08 16:32 ` joystick
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=loom.20140103T101338-556@post.gmane.org \
--to=piotr@klimek.net.pl \
--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).