From: "Nigel J. Terry" <nigel@nigelterry.net>
To: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Raid5 reshape
Date: Mon, 19 Jun 2006 17:42:41 -0400 [thread overview]
Message-ID: <44971A51.6050008@nigelterry.net> (raw)
In-Reply-To: <17558.1521.522659.91428@cse.unsw.edu.au>
Neil Brown wrote:
> On Sunday June 18, nigel@nigelterry.net wrote:
>
>> This from dmesg might help diagnose the problem:
>>
>>
>
> Yes, that helps a lot, thanks.
>
> The problem is that the reshape thread is restarting before the array
> is fully set-up, so it ends up dereferencing a NULL pointer.
>
> This patch should fix it.
> In fact, there is a small chance that next time you boot it will work
> without this patch, but the patch makes it more reliable.
>
> There definitely should be no data-loss due to this bug.
>
> Thanks,
> NeilBrown
>
>
Neil
That seems to have fixed it. The reshape is now progressing and there are no apparent errors in dmesg. Details below.
I'll send another confirmation tomorrow when hopefully it has finished :-)
Many thanks for a great product and great support.
Nigel
[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 = 7.9% (19588744/245111552)
finish=6.4min speed=578718K/sec
unused devices: <none>
[root@homepc ~]# mdadm --detail /dev/md0
/dev/md0:
Version : 00.91.03
Creation Time : Tue Apr 18 17:44:34 2006
Raid Level : raid5
Array Size : 490223104 (467.51 GiB 501.99 GB)
Device Size : 245111552 (233.76 GiB 250.99 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Jun 19 17:38:42 2006
State : clean, degraded, recovering
Active Devices : 3
Working Devices : 4
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Reshape Status : 8% complete
Delta Devices : 1, (3->4)
UUID : 50e3173e:b5d2bdb6:7db3576b:644409bb
Events : 0.3287189
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 3 65 2 active sync /dev/hdb1
3 0 0 3 removed
4 22 1 - spare /dev/hdc1
[root@homepc ~]#
next prev parent reply other threads:[~2006-06-19 21:42 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
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 [this message]
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=44971A51.6050008@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).