Hi, On 12/10/10 17:48, CoolCold wrote:
Just in case you don't know 2.6.26 branch is "frozen, not maintained" - http://wiki.openvz.org/Download/kernel/2.6.26/2.6.26-gogol.1
Yep, but that's by OpenVZ, I'm using the Debian kernel, and 2.6.26 is Debian stable, and so supported by the Debian kernel team....
The only stable for now is 2.6.18& 2.6.9 , any other is outdated/testing http://wiki.openvz.org/Download/kernel . Ongoin start is 2.6.32 as being new RHEL6 kernel. So i'd suggest you to go down to .18 or take .32 from backports.
Once RHEL6 and/or Debian6.0 has been out for a few months, I'll probably switch to 2.6.32, but I don't feel sufficiently confident to do that yet (not for OpenVZ boxes anyway - OpenVZ+2.6.32 just hasn't had enough testing-time yet for production IMO) - I also look after plenty of non-openvz 2.6.26 Debian 5.0 boxes, and if this bug is md+lvm+ext3 (which in my semi-educated opinion looks most likely, partly because there have been some similar looking deadlocks reported on non-OpenVZ Debian 5.0 systems), then it'd be preferable to track-down the cause of this and get it fixed....
Cheers, 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
