Samsung, Crucial Queued(NCQ) TRIM Data Corruption Bug Facts

Samsung, Crucial Queued(NCQ) TRIM Data Corruption Bug Facts
-----------------------------------------------------------

Issue #1
1. Linux implemented SATA 3.1 "Queued(NCQ) TRIM" support.
2. Samsung and most likely Crucial SSDs wrongly reported that "Queued(NCQ) TRIM" was supported when in fact it wasn't.
3. Samsung and Crucial SSDs behaved very badly when "Queued(NCQ) TRIM" was used.
3. Linux has since blacklisted "Queued(NCQ) TRIM" on Samsung and Crucial SSDs.
4. Linux had a bug which bypassed the Samsung and Crucual blacklist for "Queued(NCQ) TRIM", it's since been fixed.
5. OSX and Windows do not support "Queued(NCQ) TRIM" and won't for the foreseeable future.

Issue #2
1. Linux had a "Non-Queued TRIM" bug which would send the wrong blocks to the SSD to be TRIMed.
2. OSX and Windows have working "Non-Queued TRIM" support.
3. "Non-Queued TRIM" has been properly supported for quite some time on modern SSDs.

Conclusion:
1. Enabling TRIM on Windows is safe on modern SSDs. It's actually enabled by default in most cases.
2. Enabling TRIM on 3rd party SSDs in OSX using either Trim Enabler or trimforce(OSX 10.10.4 and up) is safe on modern SSDs.
3. Keeping your non-Apple SSD's firmware up to date is usually a good idea as new firmware versions usually contain bug fixes.

References:
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
http://forums.macrumors.com/threads/os-x-el-capitan-opens-door-to-trim-support-on-third-party-ssds-for-improved-performance.1891936/page-10#post-21469307