Hi, it seems...

"Some versions of the Linux kernel contain a bug which, under certain conditions, can destroy some metadata when a system is shutdown, including RAID information such as the level, chunk size and the number of devices in the array. Without this data, it is no longer possible to assemble a software RAID array; this means that payload data, while still present, is not accessible using standard methods."

"The cause of the bug was merged into the 3.2.0-22.35 kernel used in Ubuntu 12.04; a fix followed in version 3.2.0-24.38, which was released on 21 May. Pre-release versions of Linux kernels 3.4 up to RC5 (released in late April), long term kernels 3.2.14 to 3.2.16, and stable kernels 3.3.1, 3.3.2 and 3.3.3 are also affected. The problem should not be present in any of the 3.2, 3.3 or 3.4 kernel.org kernels released within the last six weeks."


Extracted from: http://www.h-online.com/open/news/it...s-1621164.html

If you run RAID arrays and other high volume data storage points, it may be wise to avoid using the -Current tree and stick to stable releases like 13.37 and such.

Bugs happen, but it's very disappointing that a potentially high-impact dataloss bug which was both introduced and found in pre-release kernel.org development kernels has managed to leak into the various maintenance/stable release branches. It defeats the whole purpose of having them!

The bug was introduced to the 3.2.y branch in 3.2.14 but slackware-current only got as far as 3.2.13, and whether you attribute that to pure luck, or Pat's innate bug-detecting spidey-sense Slackware seems to have dodged the bullet on this one. Those of us who build our own have likely been exposed at one point or another though.

I'm not sure sticking with slackware-stable is the answer though. I shudder to think what nasties are lurking in 2.6.37.6 by this point.


Out of curiosity, anyone know whether this bug made it into a RHEL?

Nope. RHEL and derivatives should be safe. Not sure about Fedora though.