SHOW:
|
|
- or go back to the newest paste.
| 1 | Samsung, Crucial Queued(NCQ) TRIM Data Corruption Bug Facts | |
| 2 | ----------------------------------------------------------- | |
| 3 | ||
| 4 | Issue #1 | |
| 5 | 1. Linux implemented SATA 3.1 "Queued(NCQ) TRIM" support. | |
| 6 | 2. Samsung and most likely Crucial SSDs wrongly reported that "Queued(NCQ) TRIM" was supported when in fact it wasn't. | |
| 7 | 3. Samsung and Crucial SSDs behaved very badly when "Queued(NCQ) TRIM" was used. | |
| 8 | 3. Linux has since blacklisted "Queued(NCQ) TRIM" on Samsung and Crucial SSDs. | |
| 9 | - | 4. OSX and Windows do not support "Queued(NCQ) TRIM" and won't for the foreseeable future. |
| 9 | + | 4. Linux had a bug which bypassed the Samsung and Crucual blacklist for "Queued(NCQ) TRIM", it's since been fixed. |
| 10 | 5. OSX and Windows do not support "Queued(NCQ) TRIM" and won't for the foreseeable future. | |
| 11 | ||
| 12 | Issue #2 | |
| 13 | 1. Linux had a "Non-Queued TRIM" bug which would send the wrong blocks to the SSD to be TRIMed. | |
| 14 | 2. OSX and Windows have working "Non-Queued TRIM" support. | |
| 15 | 3. "Non-Queued TRIM" has been properly supported for quite some time on modern SSDs. | |
| 16 | ||
| 17 | Conclusion: | |
| 18 | 1. Enabling TRIM on Windows is safe on modern SSDs. It's actually enabled by default in most cases. | |
| 19 | 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. | |
| 20 | 3. Keeping your non-Apple SSD's firmware up to date is usually a good idea as new firmware versions usually contain bug fixes. | |
| 21 | ||
| 22 | References: | |
| 23 | https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ | |
| 24 | 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 |
