Sorry, hit send too soon... On 21/09/10 23:30, Neil Brown wrote:
It is odd that 2.6.32 works and 2.6.26 doesn't as I cannot find any change between the two that could be related. There were some deadlock issues if a read-error was detected during resync but I don't think you are getting read errors are you?
Nope, no read errors.
A bisect would of course be easier for me, though not particularly easy for you....
I haven't as-yet been able to reproduce the issue without running OpenVZ on the box - I suppose the two possibilities are:
1. The bug is in the OpenVZ patches (seems unlikely given the nature of the hang, but possible I suppose). 2. The bug is only triggered by the workload which the VZ container is producing
... so without this, a bisect is a non-starter. Grrr. Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 -- 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
