From: "Nigel J. Terry" <nigel@nigelterry.net>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 reshape
Date: Sat, 17 Jun 2006 18:01:46 -0400 [thread overview]
Message-ID: <44947BCA.9040305@nigelterry.net> (raw)
In-Reply-To: <17556.31295.280083.533342@cse.unsw.edu.au>
Neil Brown wrote:
> On Saturday June 17, nigel@nigelterry.net wrote:
>
>> Any ideas what I should do next? Thanks
>>
>>
>
> Looks like you've probably hit a bug. I'll need a bit more info
> though.
>
> First:
>
>
>> [root@homepc ~]# cat /proc/mdstat
>> Personalities : [raid5] [raid4]
>> md0 : active raid5 sdb1[1] sda1[0] hdc1[4](S) hdb1[2]
>> 490223104 blocks super 0.91 level 5, 128k chunk, algorithm 2 [4/3]
>> [UUU_]
>> [=>...................] reshape = 6.9% (17073280/245111552)
>> finish=86.3min speed=44003K/sec
>>
>> unused devices: <none>
>>
>
> This really makes it look like the reshape is progressing. How
> long after the reboot was this taken? How long after hdc1 has hot
> added (roughly)? What does it show now?
>
> What happens if you remove hdc1 again? Does the reshape keep going?
>
> What I would expect to happen in this case is that the array reshapes
> into a degraded array, then the missing disk is recovered onto hdc1.
>
> NeilBrown
> -
> 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
>
>
I don't know how long the system was reshaping before the power went
off, and then I had to restart when the power came back. It claimed it
was going to take 430 minutes, so 6% would be about 25 minutes, which
could make good sense, certainly it looked like it was working fine when
I went out.
Now nothing is happening, it shows:
[root@homepc ~]# cat /proc/mdstat
Personalities : [raid5] [raid4]
md0 : active raid5 sdb1[1] sda1[0] hdc1[4](S) hdb1[2]
490223104 blocks super 0.91 level 5, 128k chunk, algorithm 2 [4/3]
[UUU_]
[=>...................] reshape = 6.9% (17073280/245111552)
finish=2281.2min speed=1665K/sec
unused devices: <none>
[root@homepc ~]#
so the only thing changing is the time till finish.
I'll try removing and adding /dev/hdc1 again. Will it make any
difference if the device is mounted or not?
Nigel
next prev parent reply other threads:[~2006-06-17 22:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 6:34 Raid5 reshape Tim
2006-06-16 6:41 ` Neil Brown
2006-06-16 16:00 ` Nigel J. Terry
2006-06-16 16:14 ` Tim T
2006-06-16 22:28 ` Neil Brown
2006-06-16 22:39 ` Nigel J. Terry
2006-06-16 22:44 ` Neil Brown
2006-06-17 19:21 ` Nigel J. Terry
2006-06-17 21:55 ` Neil Brown
2006-06-17 22:01 ` Nigel J. Terry [this message]
2006-06-17 22:05 ` Nigel J. Terry
2006-06-17 22:17 ` Neil Brown
2006-06-17 22:19 ` Nigel J. Terry
2006-06-18 12:57 ` Nigel J. Terry
2006-06-19 2:03 ` Neil Brown
2006-06-19 21:42 ` Nigel J. Terry
2006-06-19 22:46 ` Neil Brown
2006-06-19 22:53 ` Nigel J. Terry
2006-06-19 23:29 ` Mike Hardy
2006-06-19 23:33 ` Nigel J. Terry
2006-06-19 23:33 ` Neil Brown
2006-06-19 23:35 ` Nigel J. Terry
2006-06-20 10:35 ` Nigel J. Terry
2006-06-21 6:02 ` Neil Brown
2006-06-24 22:58 ` Raid5 reshape (Solved) Nigel J. Terry
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=44947BCA.9040305@nigelterry.net \
--to=nigel@nigelterry.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 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).