On Thursday February 28, gody@master.slon.net wrote: > Test results: > > It seems, that something is not still quite OK. I've got OOPS after > raidsetfaulty this time, but different than before (it looks more sublte > now). > > After reboot and another raidsetfaulty command there was no OOPS but after > activating the disk reconstruction seems stucked (now its over 15 min on > 500Mb partition): > > md2 : active raid5 hdi3[3] hdg3[1] hde3[0] > 1076224 blocks level 5, 8k chunk, algorithm 0 [3/2] [UU_] > [>....................] recovery = 0.0% (0/538112) > finish=72734.8min speed=0K/sec > This is all very weird. The info in the Oops seems to suggest memory being corrupted so something else wrong at a fairly deep level. What compiler are you using? Could you do a "make clean" and then recompile with a different compiler and see if the result is at all different? I'm probably clutching at straws here, but the oops just doesn't make sense. 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
