Announcement

Collapse
No announcement yet.

EXT4 Data Corruption Bug Hits Stable Linux Kernels

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • EXT4 Data Corruption Bug Hits Stable Linux Kernels

    Phoronix: EXT4 Data Corruption Bug Hits Stable Linux Kernels

    As a warning for those who are normally quick to upgrade to the latest stable vanilla kernel releases, a serious EXT4 data corruption bug worked its way into the stable Linux 3.4, 3.5, and 3.6 kernel series...

    http://www.phoronix.com/vr.php?view=MTIxNDQ

  • #2
    Nice, I'm on 3.6.3 right now -.-
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

    Comment


    • #3
      Great on 3.4.15 which got updated a few days ago -.-

      Comment


      • #4
        Any word on which versions of 3.4 are bad? I'm on Fedora 16 running 3.4.11 right now and haven't noticed any problems since my last reboot two days ago. I just installed the upgraded kernel 3.6.2 but luckly haven't rebooted to it yet. Thanks for the heads up, guess I'll be removing that update now.

        Comment


        • #5
          0_o dafuq im on 3.6.2 and rebooted it regurarly yesterday.

          And the fucken thing panicked after a reboot today. (but probably this was not related to this bug).

          I don't think anything got corrupted though.

          Comment


          • #6
            Originally posted by zman0900 View Post
            Any word on which versions of 3.4 are bad? I'm on Fedora 16 running 3.4.11 right now and haven't noticed any problems since my last reboot two days ago. I just installed the upgraded kernel 3.6.2 but luckly haven't rebooted to it yet. Thanks for the heads up, guess I'll be removing that update now.
            F16, installed 3.6.2, rebooted a few times since then. It's all ok for now.

            Comment


            • #7
              This is probably why, for seemingly no reason at all, my /home partition wouldn't mount yesterday on my desktop; I had to fsck it and fix a bunch of errors. Everything is fine now... phew.

              I had done a few reboots applying updates in Arch Linux, which is likely what triggered the bug (article says several reboots in rapid succession could trigger it, due to journal replaying behavior).

              Comment


              • #8
                I use ZFS with Linux 3.6.2, so I am unaffected.

                Comment


                • #9
                  TG i'm "still" using 3.6.0


                  I was to upgrade to 3.6.2 but now will wait for 3.7 anyway....it should be fully fixed by then....

                  Comment


                  • #10
                    Can the article be clarified? It seems like some people are going around saying the bug was introduced in 3.6.3 but 3.6.2 is affected too. This work machine I'm on now is running Fedora 17 with 3.6.2. No sign of an update yet.

                    Comment


                    • #11
                      So stable kernels aren't so stable.
                      What else is new?
                      That's why I run Debian... Kernel 3.2. Totally dodged this bullet.

                      Have fun with this one folks

                      Comment


                      • #12
                        I managed to get a kernel panic even with squeeze (2.6.32), the bug affected every 2.6.x/3.x kernel version.
                        This is to say I'm fine with stable releases, you can't simply expect zero bugs.
                        ## VGA ##
                        AMD: X1950XTX, HD3870, HD5870
                        Intel: GMA45, HD3000 (Core i5 2500K)

                        Comment


                        • #13
                          Originally posted by Sidicas View Post
                          So stable kernels aren't so stable.
                          What else is new?
                          That's why I run Debian... Kernel 3.2. Totally dodged this bullet.

                          Have fun with this one folks
                          Recently a change was made in ext4 in 2.6.32.y (used as many distributions' long-term support kernels) which broke GlusterFS:

                          http://joejulian.name/blog/glusterfs...ucture-change/

                          So it can and does happen... not very often, but yes.

                          Comment


                          • #14
                            DA FUQ is wrong with the stable kernels ?

                            data corruption on ext4 (again ?!)


                            luckily I didn't check and update for 3.5.7 kernel yet since this is my main production box *argh*


                            the more this happens the more I consider moving entirely to ZFS ...

                            Comment


                            • #15
                              Originally posted by zman0900 View Post
                              Any word on which versions of 3.4 are bad? I'm on Fedora 16 running 3.4.11 right now and haven't noticed any problems since my last reboot two days ago. I just installed the upgraded kernel 3.6.2 but luckly haven't rebooted to it yet. Thanks for the heads up, guess I'll be removing that update now.
                              Here is a list of affected versions:
                              • 3.4.14
                              • 3.4.15
                              • 3.5.7
                              • 3.6.2
                              • 3.6.3

                              I have filed a bug in Gentoo's bug tracker for this issue:

                              https://bugs.gentoo.org/show_bug.cgi?id=439502

                              Comment

                              Working...
                              X