> Am 20.05.2019 um 18:45 schrieb Milan Broz <gmazyland@xxxxxxxxx>: > > On 20/05/2019 16:53, Andrea Gelmini wrote: > ... >> Also, changing crypttab: >> root@glet:~# cat /etc/crypttab >> sda6_crypt UUID=fe03e2e6-b8b1-4672-8a3e-b536ac4e1539 none luks,discard >> >> removing discard didn't solve the issue. > > This is very strange, disabling discard should reject every discard IO > on the dmcrypt layer. Are you sure it was really disabled? > > Note, it is the root filesystem, so you have to regenerate initramfs > to update crypttab inside it. For me, I cannot reproduce the issue when I remove the discard option from the crypttab (and regenerate the initramfs). When trying fstrim I just get “the discard operation is not supported”, as I would expect. No damage is done to other logical volumes. However, my stack differs from Andrea’s in that I have dm-crypt on an LVM logical volume and not dm-crypt as a physical volume for LVM. Not sure if that makes a difference here. Cheers, Michael > Could you paste "dmsetup table" and "lsblk -D" to verify that discard flag > is not there? > (I mean dmsetup table with the zeroed key, as a default and safe output.) > > Milan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
