Talk:SSD

My rootfs is on LVM on LUKS. Should I trim all layers?
# lsblk NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT sda                      8:0    0 465,8G  0 disk ├─sda1                   8:1    0  94,1M  0 part └─sda2                   8:2    0 167,7G  0 part └─root (dm-0)        254:0    0 167,7G  0 crypt ├─vg2-swap (dm-1)  254:1    0     5G  0 lvm   [SWAP] ├─vg2-system (dm-2) 254:2   0    50G  0 lvm   / └─vg2-home (dm-3)  254:3    0   100G  0 lvm   /mnt/home}} --Wols (talk) 17:48, 14 March 2014 (UTC)
 * There is no reason not to, unless you care a lot about people not knowing where you have free space. The data itself is still encrypted, so it's not really an issue. It comes down to personal preference. If it's not about the wiki article, maybe the forums are a better place to discuss this?
 * Frostschutz (talk) 18:24, 14 March 2014 (UTC)

fstrim systemd timer doesn't work as intended
fstrim systemd timer section looks like it's supposed to run every twelve hours of uptime even after reboot, but won't as that's not what the persistent option does: (https://github.com/systemd/systemd/issues/3107). You should just use the one that comes with util-linux, so you can just skip creating the files and just use:

systemctl enable fstrim.timer - Peter (talk) 09:28, 3 August 2017 (UTC)

Confusion about mount options - noatime, nodiratime, relatime - for SSDs
I am always using a combination of "noatime" and "nodiratime".

Reference: SSD
 * 1) ) What would be the best mount option concerning those "atime" options?
 * 2) ) Is it wise to combine all three: noatime, nodiratime and relatime?

Keks24 (talk) 09:13, 24 November 2017 (UTC)

Mistakes in section 'XDG cache'
1) The first line of the file '/etc/profile.d/xdg_cache_home.sh' ('#!/bin/bash') should be removed. Files in '/etc/profile.d' are sourced - not executed. For that reason, a shebang line doesn't make sense. Even worse: '#!/bin/bash' may misguide a user that he can use bash syntax in this file, which is not true.

2) The section recommends to run 'env-update' after adding or modifying files in '/etc/profile.d'. That's not necessary. env-update is required after modification of a file in "/etc/env.d", but not in "/etc/profile.d".

Mike155 (talk) 01:19, 2 April 2018 (UTC)