Good day,
I have a ZFS pool where I have added a HGST HUSSL4040BSS600 SSD as special device, and a HUSMM1640ASS200 SSD as SLOG.
The pool is insanely fast, and thanks to the 12Gbps SAS, it is also very good with sync writes.
Recently, I tried
zpool trim tank
and noticed that only the HUSMM SSDs are actually trimming, and I was wondering what is going on. I found that
lsblk --discard
lists the HUSMM disks with 32G for DISC-MAX, whereas the HUSSL disks have 0B DISC-MAX. So does it mean my SSDs don't fully support TRIM aka UNMAP?
Also, according to this
I noticed that the HUSSL disks I am using had the background media scan disabled; I enabled that now and it works. And now I am wondering if, for some reason, TRIM has been disabled on these SSDs as well, and if I can enable it somehow?
I have a ZFS pool where I have added a HGST HUSSL4040BSS600 SSD as special device, and a HUSMM1640ASS200 SSD as SLOG.
The pool is insanely fast, and thanks to the 12Gbps SAS, it is also very good with sync writes.
Recently, I tried
zpool trim tank
and noticed that only the HUSMM SSDs are actually trimming, and I was wondering what is going on. I found that
lsblk --discard
lists the HUSMM disks with 32G for DISC-MAX, whereas the HUSSL disks have 0B DISC-MAX. So does it mean my SSDs don't fully support TRIM aka UNMAP?
Also, according to this
I noticed that the HUSSL disks I am using had the background media scan disabled; I enabled that now and it works. And now I am wondering if, for some reason, TRIM has been disabled on these SSDs as well, and if I can enable it somehow?