You are not logged in.
For users with solid state storage devices, TRIM can be used to inform the drive which storage blocks are no longer in use and can be wiped internally, thus preventing performance hits from spurious over-writes and write amplification.
Verify that your device supports this operation with:
lsblk -D
Then check the DISC-GRAN and DISC-MAX columns -- non-zero values indicate that TRIM can be used.
Whilst it is possible to apply TRIM with the discard filesystem option in /etc/fstab, this can cause a performance degradation because the blocks are discarded with every deletion:
https://patrick-nagel.net/blog/archives/337
https://kparal.wordpress.com/2013/05/10 … l-525-ssd/
Also, with discard enabled, any deleted data is lost completely and instantly and so recovery utilities such as extundelete will not work.
The recommended alternative to this is to apply TRIM periodically using the `fstrim` command.
For BunsenLabs, there is a systemd .timer unit that can be enabled with:
sudo cp /usr/share/doc/util-linux/examples/fstrim.{timer,service} /etc/systemd/system
sudo systemctl enable fstrim.timer
This will then run `fstrim -a` automatically once a week.
To check the status of the .timer, use:
systemctl list-timers
The .timer also integrates with the systemd journal; to view the relevant entries, use:
sudo journalctl -u fstrim.timer
Just to note: any discussion of the issues raised here can be continued in https://forums.bunsenlabs.org/viewtopic.php?id=919
Offline
Very helpful and easy to follow tutorial.
I'm wondering if this same procedure would work on other debian or ubuntu distros?
...
Linux in the backwoods of the Rocky Mountains...
Offline
I'm wondering if this same procedure would work on other debian or ubuntu distros?
Well, it certainly works in Debian:
http://forums.debian.net/viewtopic.php?f=16&t=130965
And Ubuntu also appears to ship those files:
http://packages.ubuntu.com/xenial/amd64 … x/filelist
Offline