sinisterpisces
Dabbler
- Joined
- Jan 14, 2024
- Messages
- 17
Hello,
(I've seen a similar discussion here: https://www.truenas.com/community/threads/confusing-auto-trim-description.104415/ .) However, that covers Scale and references the Linux kernel as having an impact on the answer, so I wanted to ask in the Core forum.)
I'm a new TrueNAS Core user, running the configuration in my signature.
I've set up an all SSD (SATA) pool, using 4x enterprise SSDs: SAMSUNG MZ7LH1T9 (PM 883). Specs: https://semiconductor.samsung.com/us/ssd/datacenter-ssd/pm883/mz7lh1t9hmlt/
Smartctl reports TRIM as "available, deterministic, zeroed."
How do I determine if Auto-TRIM would be preferable to the dirty block "overwrites when a device write is started" default behavior?
(I've seen a similar discussion here: https://www.truenas.com/community/threads/confusing-auto-trim-description.104415/ .) However, that covers Scale and references the Linux kernel as having an impact on the answer, so I wanted to ask in the Core forum.)
I'm a new TrueNAS Core user, running the configuration in my signature.
I've set up an all SSD (SATA) pool, using 4x enterprise SSDs: SAMSUNG MZ7LH1T9 (PM 883). Specs: https://semiconductor.samsung.com/us/ssd/datacenter-ssd/pm883/mz7lh1t9hmlt/
Smartctl reports TRIM as "available, deterministic, zeroed."
How do I determine if Auto-TRIM would be preferable to the dirty block "overwrites when a device write is started" default behavior?
