Am I damaging my SSD by not setting discard_max_bytes to a proper value and still running TRIM?
- /RaspberryPi
- Corporate
- Posts: 2449
- Joined: Wed Jun 05, 2019 1:29 am
Am I damaging my SSD by not setting discard_max_bytes to a proper value and still running TRIM?
Hi!
I've followed Jeff Geerling's guide to enable TRIM on an SSD connected via USB-SATA adapter (it reports to be a JMS561U chipset). I've been able to complete all the steps except editing the discard_max_bytes to set a proper value. The value already in the file is 4294966784. According to the guide, it should be 3355392 (65535*512 -- big difference). When I try to edit the file as root, I always get "invalid argument". Moreover, the value found in discard_max_hw_bytes is exactly the same as the one present in discard_max_bytes, 4294966784.
Also (and I don't know if this is relevant?), when I run lsblk -D, I see that the discard capability of the disk is 4G. Also, If I run lsusb -t I see that uas driver is being used. And when I run fstrim -v / it seems to work -- it reports that it's trimmed some MBs.
My question is: Is TRIM working or am I doing damage to my disk by not having a proper value for the discard bytes?
Thanks!!
submitted by /u/Mrs-Anders
[link] [comments]
Source: https://www.reddit.com/r/raspberry_pi/c ... scard_max/
/RaspberryPi