[opensuse-factory] Kernel 5.1 possibly affected by "fstrim discarding too many or wrong blocks, leading to data loss" ?
Seehttps://bugs.archlinux.org/task/62693, especially the identified "bad commit". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Pujos writes:
See https://bugs.archlinux.org/task/62693, especially the identified "bad commit".
My swap partition (via dm/lvm) was found with the first 52MB or so zeroed on the third boot into kernel 5.1.2. The first boot was only to get rid of the MOK tool diversion in the boot manager, so likely the system didn't use the swap during the roughly two minutes it was up. The second boot however had me use the box for a whole day, and it typically uses a few dozen MB of swap after some time. I think the default is to do a trim on discarded swap if it resides on an SSD. Besides the zeroed blocks in /dev/mapper/system-swap I have found no inconsistencies in the root fs, but I'm not sure how to check the much larger /home /which is xfs) since apparently the kernel doesn't support the kernel scrubbing facility. The fsck at boot didn't complain about anything, but it likely also didn't do anything beyond checking that the dirty flag was cleared. I have not recreated the swap signature yet, are there any special parameters that I need to use on mkswap? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Achim Gratz
-
Michael Pujos