Hi, On multiple of my machines I have the root filesystem on a dm-crypt device placed on an SSD. Now, I would like to use `fstrim /`. Now, I know about the security implications. But, as encryption for me primarily is a way to be able to throw out disks without further effort, I don't consider those a problem for me. Sadly, on any system I installed directly with Leap 15.0 I cannot get this to work. Despite having `rd.luks.options=discard` in my kernel arguments I get the following output from `lsblk`: # lsblk --discard /dev/sda NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 ├─sda2 0 512B 2G 0 └─sda3 0 512B 2G 0 └─cr_sda3 0 0B 0B 0 Curiously the same works on a different systems which has been upgraded through various versions of Leap and is now also running on 15.0. # lsblk --discard /dev/sda NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 ├─sda2 0 512B 2G 0 ├─sda3 0 512B 2G 0 ├─sda4 0 512B 2G 0 ├─sda5 0 512B 2G 0 └─sda6 0 512B 2G 0 └─luks-081…3e1 0 512B 2G 0 The only difference I can see between the systems is, that the older system uses the UUID instead of the name, and for some reason the newer system does have the device containing root in `/etc/crypttab` while the old system does not. Any hints on what might be causing the different behavior? Kind Regards, Matthias -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke