Slashdot Mirror
Data-Corrupting ext3 Bug In Linux 2.4.20
linuxjack55 writes "Kerneltrap is reporting a data-corrupting bug in the ext3 code of kernel 2.4.20. The scope of the problem (and workarounds) are described in the article, which also includes a link to an interesting interview with kernel hacker Andrew Morton. In it, he states that the '2.4.x core has only stabilized very recently' and the 2.4.x kernel is 'even now...in a late beta state.' He was also asked when the 2.4 kernel could be considered stable. His reply: 'Six months, perhaps?' If that prediction is accurate, 2.6.x could arrive before a 'stable' version of 2.4.x does." (The interview with Morton is from last February -- how stable you consider 2.4 right now is up to you.)
this is a first post
the editor's are on crack again
let's beat the dead horse
Because, the corruption of the databases would explain the duplicate story postings. Come on guys, ride this one for all it's worth.
Overrated / Underrated : Moderation
Andrew Morton then continued... 'One popular company to be affected by the bug was the OSDN. Their technology news site Slashdot.org updated their database server with the new 2.4.20 kernal.'
It was a disaster. 'The problem was with syncing during unmount. When the people at Slashdot upgraded, their databases became corrupted. Suddenly, duplicate stories began to appear!'
Added Andrew, 'Wow, duplicate stories. There's a shocker'
The full interview will be availible soon on The Onion