From: Redeeman <redeeman@metanurb.dk>
To: linux-raid@vger.kernel.org
Subject: problem in grow of raid5 3 -> 4 disks
Date: Tue, 17 Feb 2009 21:48:11 +0100 [thread overview]
Message-ID: <1234903691.18827.21.camel@localhost> (raw)
Hello.
A friend of mines array just stalled in the reshape process, while
growing from 3 to 4 disks, on raid5.
kernel is 2.6.27,
dmesg spews insane amounts of:
compute_blocknr: map not correct
compute_blocknr: map not correct
compute_blocknr: map not correct
compute_blocknr: map not correct
/proc/mdstat:
md0 : active raid5 sdd1[3] sdc1[2] sdb1[1] sda1[0]
1953519872 blocks super 0.91 level 5, 64k chunk, algorithm 2 [4/4]
[UUUU]
[==============>......] reshape = 73.2% (715827840/976759936)
finish=15504.9min speed=280K/sec
# mdadm --detail:
/dev/md0:
Version : 0.91
Creation Time : Sun Feb 1 03:30:50 2009
Raid Level : raid5
Array Size : 1953519872 (1863.02 GiB 2000.40 GB)
Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Feb 17 23:26:37 2009
State : clean, recovering
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Reshape Status : 73% complete
Delta Devices : 1, (3->4)
UUID : e55b3e10:456492af:b4421a5d:cd497c91
Events : 0.476018
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
What should we do about this? Anyone experienced something similar?
SMART reports no errors on any of the disks.
---
Thanks.
Kasper Sandberg
next reply other threads:[~2009-02-17 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:48 Redeeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 21:12 problem in grow of raid5 3 -> 4 disks Redeeman
2009-02-18 1:52 ` Kasper Sandberg
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=1234903691.18827.21.camel@localhost \
--to=redeeman@metanurb.dk \
--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).