Announcement

Collapse
No announcement yet.

Linux 4.14.2 Fixes The BCache Corruption Bug

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

  • Linux 4.14.2 Fixes The BCache Corruption Bug

    Phoronix: Linux 4.14.2 Fixes The BCache Corruption Bug

    Normally I don't bother mentioning new Linux kernel point releases on Phoronix unless there are some significant changes, as is the case today with Linux 4.14.2...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    And this is why I stick to the previous LTS for a couple months.

    Comment


    • #3
      Originally posted by RealNC View Post
      And this is why I stick to the previous LTS for a couple months.
      And probably why 4.9 is still the latest marked as "longterm" on kernel.org.

      Comment


      • #4
        Code:
        edgar444@Fold-Gentoo ~ $ uname -r
        4.14.1-gentoo
        Lucky I don't use bcache! xD

        Comment


        • #5
          Originally posted by edgar444 View Post
          Code:
          edgar444@Fold-Gentoo ~ $ uname -r
          4.14.1-gentoo
          Lucky I don't use bcache! xD
          Yes, but replace bcache with whatever you use here and if it happened to you, wouldn't be so lucky.

          A reminder to always have fresh backups, locally and on the cloud, just in case. Clonezilla is great.

          Comment


          • #6
            "The COW filesystem for Linux that won't eat your data" lol

            Comment


            • #7
              Originally posted by pal666 View Post
              "The COW filesystem for Linux that won't eat your data" lol
              bcachefs ( http://bcachefs.org/ ) is not the same as bcache ( https://bcache.evilpiepirate.org/ )
              Last edited by ipsirc; 24 November 2017, 03:15 PM.

              Comment


              • #8
                Originally posted by ipsirc View Post
                bcachefs ( http://bcachefs.org/ ) is not the same as bcache ( https://bcache.evilpiepirate.org/ )
                did you read your links?
                "Bcache is done and stable - but work hasn't stopped. Bcachefs is the hot new thing: a next generation, robust, high performance copy on write filesystem. You could think of it as bcache version two, but it might be more accurate to call bcache the prototype for what's happening in bcachefs - incrementally developing a filesystem was part of the bcache plan since nearly the beginning."
                "[bcachefs]'s building on top of a codebase with a pedigree - bcache already has a reasonably good track record for reliability"
                Last edited by pal666; 25 November 2017, 10:57 AM.

                Comment


                • #9
                  Yes, I've read.

                  Comment


                  • #10
                    I actually ran into this issue with bcache+btrfs as I posted here:
                    ​​​​​​https://www.phoronix.com/forums/foru...957#post988957

                    I saw a bcache related issue fixed in 4.14.2 (but not in 3.15.16 which came out at the same time, but since 3.15 never had the issue I figured this was the fix I needed) and upgraded finding that it fixed the issue for me yesterday or so. Now that I have working nightly backups and I know how to fix btrfs for this issue, I figured it was pretty safe to try.

                    I can confirm that 4.14.2 definitely fixes it for me across several machines.

                    If you ran into this issue with btrfs, check out my link above for a potential method to recover (after you've reverted to a safe kernel).

                    Comment

                    Working...
                    X