Hi,
I'm using a raid 5 with 4*400 GB PATA disks on a rather old VIA
mainboard, running centos 5.0. a few days ago the server started to
reboot or freeze occasionally, after reboot md always starts a resync
of the raid:
$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5
Rainer Fuegenstein wrote:
1) when md starts a resync of the array, shouldn't one drive be marked
as down [_UUU] in mdstat instead of reporting it as [] ? or, the
other way round: is hde really the faulty drive ? how can I make sure
I'm removing and replacing the proper drive ?
If it is
On Monday September 24, [EMAIL PROTECTED] wrote:
Hi,
I'm using a raid 5 with 4*400 GB PATA disks on a rather old VIA
mainboard, running centos 5.0. a few days ago the server started to
reboot or freeze occasionally, after reboot md always starts a resync
of the raid:
$ cat /proc/mdstat
Thanks for this and the other 2 patches. They are all in the mdadm
.git.
Thanks,
NeilBrown
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Friday September 7, [EMAIL PROTECTED] wrote:
Neil, could this be a bug?
Sure could. Thanks for the report.
This patch (already in .git) should fix it.
NeilBrown
---
Don't corrupt 'supertype' when speculatively calling load_super1
When load_super1 is trying to
