Arch Linux

860lacov

Member

Registered: 2020-05-02

Posts: 480

[SOLVED] discard=asyns is not working (probably)

Is my assumption correct? How to fix this?

Today I did:
sudo fstrim -av
/boot: obcięto 791,2 MiB (bajtów: 829673472) na urządzeniu /dev/nvme0n1p1
/: obcięto 957,1 GiB (bajtów: 1027715575808) na urządzeniu /dev/mapper/cryptroot

So almost 1TB of data trimed

The drive is 2TB Samsung nvme.

FS: btrfs
fstab: rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,commit=120,subvol=@home    0 0
bootloader entry: rd.luks.options=discard,password-echo=no root=/dev/mapper/cryptroot rootflags=subvol=@ rw quiet loglevel=3 systemd.show_status=auto rd.udev.log_level=3 amd_pstate=guided

Last edited by 860lacov (2025-04-08 19:42:09)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,273

Re: [SOLVED] discard=asyns is not working (probably)

fstrim basically  always lists the entirety of the drive it operates on, it doesn't calculate how much effective data it trims, you can't really make any assertion from this message.

Last edited by V1del (2025-04-03 22:35:06)

860lacov

Member

Registered: 2020-05-02

Posts: 480

Re: [SOLVED] discard=asyns is not working (probably)

fstrim basically always lists the entirety of the drive it operates on, it doesn't calculate how much effective data it trims, you can't really make any assertion from this message.

Thanks!
And could (or should) I do to test if it works properly? I didn't see any signs that there is something wrong.