Results 1 to 5 of 5

Thread: Kernel 5.1: fstrim bug potentially causing data loss?!

  1. #1

    Default Kernel 5.1: fstrim bug potentially causing data loss?!

    Just came across this one: https://bugs.archlinux.org/task/62693
    It was mentioned in the openSUSE factory mailing list.The title says all about a potentially massive data loss.

    Please, what now? Disable fstrim immediately? What about the circumstances mentioned? Is a Btrfs root partition (unencrypted) safe? I figure there is no easy way of going back to kernel 5.0 with Tumbleweed where only two kernel versions are installed simultaneously; I figure it might not be worth it to revert to an older Btrfs snapshot (never had to up to now).

  2. #2

    Default Re: Kernel 5.1: fstrim bug potentially causing data loss?!


  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    11,995
    Blog Entries
    3

    Default Re: Kernel 5.1: fstrim bug potentially causing data loss?!

    Hard to know for sure. But it looks as if you are safe with unencrypted "btrfs" (because that does not use the device-mapper).

    As for going back to a 5.0 kernel -- that would be easy here. I will have a 5.0 kernel available until a 5.2 kernel arrives.

    What I do, is add "oldest" to the criteria for keeping kernels:
    Code:
    multiversion.kernels = oldest,latest,latest-1,running
    (that's a line in "/etc/zypp/zypp.conf"). That kept a 4.20 kernel around for a while. But once 5.1 arrived, I deleted the 4.20 kernel. So now the last 5.0 kernel was the oldest and will be kept around until I delete that. This seems like a good safety move with Tumbleweed.
    openSUSE Leap 15.1; KDE Plasma 5;

  4. #4

    Default Re: Kernel 5.1: fstrim bug potentially causing data loss?!

    Quote Originally Posted by nrickert View Post
    As for going back to a 5.0 kernel -- that would be easy here. I will have a 5.0 kernel available until a 5.2 kernel arrives.What I do, is add "oldest" to the criteria for keeping kernels:
    Code:
    multiversion.kernels = oldest,latest,latest-1,running
    (that's a line in "/etc/zypp/zypp.conf"). That kept a 4.20 kernel around for a while. But once 5.1 arrived, I deleted the 4.20 kernel. So now the last 5.0 kernel was the oldest and will be kept around until I delete that. This seems like a good safety move with Tumbleweed.
    Oh yes, multiversion.kernel sounds good. Unfortunately, I am not sure what the default behavior of a fairly recent TW install is, since I am not at my PC until tomorrow. I know for sure it keeps two kernels only, but I am not sure whether I have two 5.1 versions, i.e. 5.1.3 and 5.1.2 as per the TW default and successive zypper dup's, or whether I have a 5.1 and a 5.0. Uhhh...Ugly stuff with such a kernel bug , and with the bug occurrence conditions still being murky.

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,397

    Default Re: Kernel 5.1: fstrim bug potentially causing data loss?!

    Last of each kernel point release is available to those who don't mind a little repositories/ digging. I'm not including any whole URL because Takashi did not when he announced this:
    https://lists.opensuse.org/opensuse-.../msg00153.html
    repositories/home:/tiwai:/kernel:/
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •