fstrim.service похоже не работает

nafanja
вот оттримь раздел, а потом еще раз, и в выводе ничего не изменится

 sudo fstrim --fstab --verbose
/: 0 B (0 bytes) trimmed on /dev/sda2

 sudo fstrim --fstab --verbose
/: 4,6 GiB (4920778752 bytes) trimmed on /dev/sda2

nafanja
вот оттримь раздел, а потом еще раз, и в выводе ничего не изменится.

$ sudo fstrim -av
/: 129,2 GiB (138685329408 bytes) trimmed on /dev/sda1

$ sudo fstrim -av
/: 48 MiB (50282496 bytes) trimmed on /dev/sda1

$ df -h | rg sda1
/dev/sda1          234G         105G  118G           48% /

root@b ~ # fstrim -av
/tmp: 0 B (0 bytes) trimmed on /dev/zram0
/boot/efi: 63,6 MiB (66672640 bytes) trimmed on /dev/sda1
/: 25,8 GiB (27659444224 bytes) trimmed on /dev/sda3
fstrim -av  0,00s user 6,31s system 0% cpu 16:12,83 total
root@b ~ # fstrim -av
/tmp: 0 B (0 bytes) trimmed on /dev/zram0
/boot/efi: 63,6 MiB (66672640 bytes) trimmed on /dev/sda1
/: 25,8 GiB (27656572928 bytes) trimmed on /dev/sda3
fstrim -av  0,01s user 6,55s system 0% cpu 16:11,06 total
root@b ~ # fstrim -av
/tmp: 0 B (0 bytes) trimmed on /dev/zram0
/boot/efi: 63,6 MiB (66672640 bytes) trimmed on /dev/sda1
/: 25,9 GiB (27736104960 bytes) trimmed on /dev/sda3
fstrim -av  0,01s user 5,56s system 0% cpu 16:16,95 total

UUID=4432f74b-a439-48cc-96e6-226c7902d714 /                 btrfs   defaults,compress-force=zstd,subvol=@archlinux_root             0       1
UUID=4432f74b-a439-48cc-96e6-226c7902d714 /.snapshots       btrfs   defaults,compress-force=zstd,subvol=@archlinux_root_snapshots   0       0
UUID=4432f74b-a439-48cc-96e6-226c7902d714 /home             btrfs   defaults,compress-force=zstd,subvol=@home_all                   0       2
UUID=4432f74b-a439-48cc-96e6-226c7902d714 /home/.snapshots  btrfs   defaults,compress-force=zstd,subvol=@home_all_snapshots         0       0

/dev/sda3 on / type btrfs (rw,relatime,compress-force=zstd:3,ssd,space_cache,subvolid=261,subvol=/@archlinux_root)
/dev/sda3 on /.snapshots type btrfs (rw,relatime,compress-force=zstd:3,ssd,space_cache,subvolid=262,subvol=/@archlinux_root_snapshots)
/dev/sda3 on /home type btrfs (rw,relatime,compress-force=zstd:3,ssd,space_cache,subvolid=266,subvol=/@home_all)
/dev/sda3 on /home/.snapshots type btrfs (rw,relatime,compress-force=zstd:3,ssd,space_cache,subvolid=265,subvol=/@home_all_snapshots)

nafanja
дописал к корню в fstab опцию discard,

Enabling TRIM support on the file system

This is the most interesting part. Most people simply add the option “discard” in the mounting options at /etc/fstab. However, this means that every time you delete a file, the OS will be reporting in real-time to the SSD which blocks were occupied by that file and are not longer in use, and then the SSD will have to perform a defragmentation and deletion of those internal blocks, operation which will take an amount of time higher than desired.

In order to optimize the performance of the SSD, I strongly advise you to avoid doing the TRIM operation in real time (whenever a file is deleted) because you would be putting an unnecessary extra amount of work over the SSD. In other words: You should not enable the discard option in fstab.

Instead, what I recommend is to run a script periodically to tell the SSD which blocks are free with the command fstrim. Doing this operation daily or weekly is more than enough. This way we do not lose any performance due to TRIM when deleting files and we periodically keep informed the SSD about the free blocks.

vasek
Enabling TRIM support on the file system

This is the most interesting part. Most people simply add the option “discard” in the mounting options at /etc/fstab. However, this means that every time you delete a file, the OS will be reporting in real-time to the SSD which blocks were occupied by that file and are not longer in use, and then the SSD will have to perform a defragmentation and deletion of those internal blocks, operation which will take an amount of time higher than desired.

In order to optimize the performance of the SSD, I strongly advise you to avoid doing the TRIM operation in real time (whenever a file is deleted) because you would be putting an unnecessary extra amount of work over the SSD. In other words: You should not enable the discard option in fstab.

Instead, what I recommend is to run a script periodically to tell the SSD which blocks are free with the command fstrim. Doing this operation daily or weekly is more than enough. This way we do not lose any performance due to TRIM when deleting files and we periodically keep informed the SSD about the free blocks.

nafanja
дописал к корню в fstab опцию discard