2009/10/11 Steinar H. Gunderson <sgunderson@xxxxxxxxxxx>: > Hello, > > I've just upgraded from 2.6.31-rc8 to 2.6.32-rc3, and I thought I would turn > on the new multicore RAID-5 processing. I did, it booted up and started > syncing RAIDs (since the last shutdown before that was not clean), and > started syncing at the minimum speed (1000 K/sec). I've seen this before, so > I upped it in /proc to about 100MB/sec minimum (which is well below what I've > seen from that RAID; six 7200rpm SATA drives connected by SAS). > > However, it never wanted to go above about 8-10MB/sec, and md4_raid5 used > 100% CPU while I/O was extremely slow. Suddenly the serial console flashed: > < snip > Hi, I'm not savvy enough to read traces, but on surface it looks similar to a problem described in a thread started on the linux-raid list by Holger Kiehl on Oct. 16. (Raid reconstructing and process hanging in D state). Hope it helps. Regards, Paweł -- 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
