Does NVMe m.2 SSD need to enable and start fstrim.timer?
Welcome!
(Sorry, I’m inexperienced :()
Does NVMe M.2 SSD need to enable/start fstrim.timer?
-
There is written “write below the arrow” and not “write within both arrows”. I corrected that for you.
-
A NVME/SSD needs to be trimmed in general yes. Older SSDs you are better of using a periodic trim, because of the amount of wear off. Newer SSDs shouldn’t have a problem to be continuous trimmed (discard via filesystem).
Solid state drive - ArchWiki
There is a fstrim timer that can be enabled I believe it trims weekly.
Thank You!
M.2 SATA SSD - this need TRIM?
And there is an M.2 NVMe SSD - which does not need SATA
TRIM command?
Every SSD needs to be trimmed from time to time at least.
I agree with ChatGPT:
What happens if I never trim my SSD?
Decreased Performance:
- Slower Write Speeds: Without TRIM, the SSD must perform additional operations to prepare free space for new data. This extra step, called “garbage collection,” involves moving existing data around and erasing blocks, which slows down write operations.
- Increased Latency: The time required to write data increases because the SSD must first clear space before writing new data, leading to higher latency.
Reduced Lifespan:
- Wear Leveling: SSDs have a limited number of write cycles. Without TRIM, wear leveling algorithms are less efficient because the drive has incomplete information about which blocks are actually free. This can lead to uneven wear and shorten the SSD’s lifespan.
- Increased Write Amplification: Without TRIM, more data must be moved around and erased during garbage collection, increasing write amplification. Higher write amplification accelerates the wear on the NAND cells, further reducing the drive’s lifespan.
Fragmentation:
- Internal Fragmentation: Although SSDs do not suffer from fragmentation in the same way as HDDs, lack of TRIM can cause internal fragmentation. This means that data is scattered across the SSD, making garbage collection less efficient and further impacting performance.
Capacity Management:
- Less Accurate Free Space Reporting: Without TRIM, the SSD’s internal controller cannot accurately determine which blocks are free. This can lead to the drive incorrectly managing its available space, potentially leading to more aggressive garbage collection and further performance degradation.
Data Integrity Risks:
- Overprovisioning Stress: Many SSDs reserve a portion of their capacity as overprovisioning space to help manage write operations and wear leveling. Without TRIM, this space may be used less efficiently, increasing the risk of data errors or corruption over time.
In summary, regularly trimming your SSD is essential to maintain its performance, lifespan, and overall health. Most modern operating systems support automatic TRIM commands, so it’s generally a good idea to ensure this feature is enabled for optimal SSD operation.
There is no such a thing like “SATA TRIM”. Please inform yourself what “TRIM” actually means. The wiki article explains it.
"There is no such a thing like “SATA TRIM”. " ??
What is TRIM?
TRIM is a command for the ATA (Advanced Technology Attachment) interface.
Sure, there is a TRIM command for ATA, but not a “SATA TRIM”. Terminology matters. There is only one not a special one for ATA and PCIE. So just call it the TRIM COMMAND.
The essence of my question would have been that the NVMe Controller does not do the same “in house” as TRIM does in the case of a SATA SSD?
Look there are just 2 different protocols. Both can and need to a handle the trim request. A SATA SSD and M.2 SSD just differs in how it is connected and which protocol should be used. “In house” it is exactly the same command.
It is just like downloading a file via FTP://
or HTTP://
Different protocol, but the file is the same.
Ok. … You convinced me!
Manjaro installed on a Samsung 990 Pro NVMe M.2 SSD. It’s timed and the manual fstrim also runs!
If you have installed with btrfs, it would be advantageous for the NVMe SSD to use a continuous trim instead of the weekly trim.
To do this, you must add the entry discard=async
for the respective partitions in /etc/fstab.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.