How do I enable it in case it isn’t?
It’s enabled, the screenshot has all the information. It will be triggered weekly, the next run is in 1 day and 1 hours.
[Edit] If you think the drive currently doesn’t have support you can also check the information on the page below:
Then why does the
sudo fstrim /
Return
discard operation is not supported
?
So it is scheduled, but the operation fails every time? Where do I see whether all the previous ones were successful or not?
I used this script to check unencrypted Trim: ssd - Trim with LVM and dm-crypt - Unix & Linux Stack Exchange
I’m not sure how that would work with Kinoite, and LUKS iirc needed a setting to allow Trim to actually affect the SSD (something like trimmed cells leaking the fact it was encrypted). That ordeal alone had me drop the concept of encryption on SSDs along with LVM years ago.
1 Like
Added luks2 and removed kde, kde-plasma, luks1
cryptsetup --allow-discards --persistent refresh luks-643dc0f7-c876-4e37-9207-5c053a75fc70
Seems to have helphed, the TRIM command now returns no output (meaning it ran successfully). But I am still confused about all the previous scheduled operations
Yeh.
dmsetup table luks-blablabla-bla-bla-bla-blablabla
and
cryptsetup luksDump /dev/nvme0n1p3 | grep Flags
don’t show allow-discards
So what is the purpose of the discard option in /etc/crypttab?
Perhaps it wouldn’t be a bad idea to file a ticket about this somewhere? It seems the procedure for enabling Trim could benefit from some extra streamlining.
Preferrably the user would be notified about missing support so that they can take action, if this is feasible.
Trim seems important enough for SSDs that it feels suboptimal to let the systemd timer just silently fail in the background.
https://fedoraproject.org/wiki/Changes/EnableTrimOnDmCrypt
https://fedoraproject.org/wiki/Changes/EnableFSTrimTimer
Interesting… i can’t really tell from the EnableTrimOnDmCrypt entry if this means that support should be available by default for LUKS, is that the case?