Announcement

Collapse
No announcement yet.

Linux 5.1 Hit By A Data Loss Bug Due To Overly Aggressive FSTRIM

Collapse
X
Collapse
 
  • Page of 5
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 template Next
  • #1

    Linux 5.1 Hit By A Data Loss Bug Due To Overly Aggressive FSTRIM

    Phoronix: Linux 5.1 Hit By A Data Loss Bug Due To Overly Aggressive FSTRIM

    As a forewarning to those using LVM, dm-crypt, and Samsung solid-state drives, this combination in some manner(s) may lead to data corruption if using the Linux 5.1 kernel...

    Linux 5.1 Hit By A Data Loss Bug Due To Overly Aggressive FSTRIM - Phoronix
    http://www.phoronix.com/scan.php?page=news_item&px=Linux-5.1-FSTRIM-Bug
    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
    Tags: None
  • #2
    Could this also effect veracrypt as it uses dm-crypt? , i've had 3 desktop (can still ssh with no errors seen) lockups during high disk IO since 5.1, been fine back on 5.0.

    Comment

    • #3
      Big thanks for this warning.. I was just considering upgrading to 5.1...
      • Likes 4

      Comment

      • #4
        Maybe this is what I have been seeing under VirtualBox since just recently? Are Windows FSTRIM's passed on to the underlying device in VirtualBox?

        Comment

        • #5
          Originally posted by gQuigs View Post
          Big thanks for this warning.. I was just considering upgrading to 5.1...
          Yes, big thanks. My main system fulfills all of those conditions and I've been running Linux 5.1.3 for a few days. Immediately reverted to 4.19 when I saw the warning.
          • Likes 1

          Comment

          • #6
            Oh, crap, this is exactly me. Fedora 29 with a Samsung SSD and an excrypted drive. I manually turned on the 'pass discards' setting in the LVM config.

            Hope Fedora doesn't ship 5.1 before this gets fixed!
            • Likes 1

            Comment

            • #7
              Fedora has already posted a fix: https://koji.fedoraproject.org/koji/...uildID=1270326
              • Likes 5

              Comment

              • #8
                Pretty sure my work laptop hits all of these criteria, except for maybe the Samsung SSD bit. It's a dm-crypt encrypted partition with discards passed through and is running 5.1.3, just not sure about the SSD manufacturer.

                Definitely going to check on Monday.
                • Likes 2

                Comment

                • #9
                  Originally posted by willmore View Post
                  Oh, crap, this is exactly me. Fedora 29 with a Samsung SSD and an excrypted drive. I manually turned on the 'pass discards' setting in the LVM config.

                  Hope Fedora doesn't ship 5.1 before this gets fixed!
                  Fedora had 5.1 in testing, so as long as you never had the testing repo enabled you should be good.
                  • Likes 2

                  Comment

                  • #10
                    So just using Samsung SSDs is not enough to get this problem? Using 5.1.4 right now.
                    • Likes 2

                    Comment

                    Previous 1 2 3 4 5 template Next
                    Working...
                    X