On Thursday July 3, jbuckingham@xxxxxxxxxxxxxxxx wrote: > Hi Neil > > So, a little while ago I did upgrade the kernel > (2.6.22.18-0.2-default), but it did not seem to make any difference to the I was thinking more like 2.6.25. My guess is that the fix was commit 25156198235325805cd7295ed694509fd6e3a29e which is in 25-rc4. > 'echo sync > /sys/block/md3/md/sync_action'. > > After receiving your latest email, I did the following... > > echo sync > /sys/block/md3/md/sync_action > (device busy reported to konsole as before) > echo idle > /sys/block/md3/md/sync_action > echo sync > /sys/block/md3/md/sync_action > (device busy reported to konsole as before) > > Then checked "top" - and saw significant activity from > md3_sync and md3_raid5 processes. I think the resync thread was sort of "half-started". Writing 'idle' killed it off, then it was automatically restarted and proceeded properly. Thanks for reporting your success. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
