Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

As far as how you get hit by this EXT4 bug, Ted says, "Well, the problem won't show up if the journal has wrapped. So it will only show up if the system has been rebooted twice in fairly quick succession.

Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

It would be really of great utility to know and find out what is meant by "...don't reboot your system too quickly..." in order to minimize the risk as much as possible until a fix will hit a new stable kernel release.

Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

I'm so glad I forgot to update my machine. It's thankfully running Kernel 3.6.2!Is there anyway to update all packages, but leave one out (like Linux, for example)?

Last edited by oldtimeyjunk (2012-10-24 14:05:47)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." - Unix for Dummies, 2nd Edition

Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

For those who think they are safe with 3.6.2: please read the topic and the Phoronix post again:

Ted Ts'o wrote:

I think I've found the problem. I believe the commit at fault is commit 14b4ed22a6 (upstream commit eeecef0af5e):

jbd2: don't write superblock when if its empty

which first appeared in v3.6.2.

My laptop is running 3.6.2, and I've done countless reboots, including having to go through several accidental power outages when I've not had a battery in. Nothing has happened...

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." - Unix for Dummies, 2nd Edition

Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

Even though it is a severe bug the chances of it happening to you are low. You have to unmount and immediately remount an EXT4 partition twice in a row for it to happen. On a normally operating system that is not a normal thing to happen. Just wait on your desktop for 5 minutes before rebooting again.

Arch, as a general rule, tends to stick as close to upstream as possible. I'm sure the devs are very competent people but a quick hack or branch revert has the possibility of introducing issues of its own. With the chance of the bug occurring low on a normally operating system I think it is better to wait for a fix from upstream.

Re: [SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

headkase wrote:

Even though it is a severe bug the chances of it happening to you are low. You have to unmount and immediately remount an EXT4 partition twice in a row for it to happen. On a normally operating system that is not a normal thing to happen. Just wait on your desktop for 5 minutes before rebooting again.

Arch, as a general rule, tends to stick as close to upstream as possible. I'm sure the devs are very competent people but a quick hack or branch revert has the possibility of introducing issues of its own. With the chance of the bug occurring low on a normally operating system I think it is better to wait for a fix from upstream.

Well maybe i am a bit over stressed about this since with this computer i have quite a lot of troube which i cannot find solutions to. Also a kernel panic after a reboot this morning -probably not related to this- got me in a bad mood.