TRIM on manually mounted encrypted SSD
Hi all,
I have a second PCIe slot in my Lenovo laptop which I use for a second SSD drive in addition to an NVMe where my system is installed. I have encrypted this drive with dmcrypt and mount it manually after boot up. Putting the drive into /etc/fstab makes my Ubuntu 16.10 (upgraded from 16.04) fail to boot or boot so slowly it is not acceptable. I haven't looked into this issue. To keep the second SSD fast I want have its cells 'cleaned up' via the trim command. It is formatted with the XFS file system. There is a weekly cron job for all mounted file systems, but the second SSD seems to be getting slower. When I execute the fstrim command manually on all mounted file systems, the SSD drive is left out: Code:
# /sbin/fstrim -v --all || true Code:
cat /var/log/syslog | grep fstrim If you need more information, let me know. |
The partition is encrypted. You have to allow the trim operation also in the encryption layer, otherwise the operations from the filesystem layer never actually hit the drive controller. From "man cryptsetup":
Quote:
|
TRIM on manually mounted encrypted SSD
No. Trim is installed by the installer though but the 2 have no correlation. Trim is enabled based on the brand of your SSD. If the SSD is supported and tested prior and deemded working perfectly trim will be enabled. Otherwise it will be installed and disabled and you need to enable it manually. This is independent of the installer.
So, one installation might have you a working trim from the start; another installation might have you needing to enable it manually. If not, how could I enable it after the installation? Code:
From fstrim: |
All times are GMT -5. The time now is 07:25 PM. |