I tried the stock 2.6.38-8-server (natty) with 5 drives on an mvsas card, running badblocks simultaneously.
They worked for about 10 minutes, but then all 5 had errors similar to those reported above.
I tried manjo's kernel (2.6.32-19-generic) and 4 out of 5 survived a full badblocks read. Those four also
survived a write cycle, but when the badblocks processes switched to the read (verify) part, IO hung
with:
mvs_abort_task() mvi=ffff880408dc0000 task=ffff88040941ea80 slot=ffff880408de44b8 slot_idx=x0
errors.
In the past, I have had great success with Andy Yan's patches, but when I applied them to 2.6.38-8-server
they made the problems worse, likely because I did the merge badly. I will try re-doing the merge. In the
mean time, manjo, could you post your diff so that I can see how you resolved some of the conflicts?
I tried the stock 2.6.38-8-server (natty) with 5 drives on an mvsas card, running badblocks simultaneously. c0000 task=ffff880409 41ea80 slot=ffff880408 de44b8 slot_idx=x0
They worked for about 10 minutes, but then all 5 had errors similar to those reported above.
I tried manjo's kernel (2.6.32-19-generic) and 4 out of 5 survived a full badblocks read. Those four also
survived a write cycle, but when the badblocks processes switched to the read (verify) part, IO hung
with:
mvs_abort_task() mvi=ffff880408d
errors.
In the past, I have had great success with Andy Yan's patches, but when I applied them to 2.6.38-8-server
they made the problems worse, likely because I did the merge badly. I will try re-doing the merge. In the
mean time, manjo, could you post your diff so that I can see how you resolved some of the conflicts?