3 ms·
The drives we have detected the issue had still un-queued TRIM. I have reached to one of the kernel I/O developers for help and he confirmed that it is not rela
by adamsurak 11y ago
The drives we have detected the issue had still un-queued TRIM. I have reached to one of the kernel I/O developers for help and he confirmed that it is not related.
- asayler 11y agoBut isn't the blacklist you link to in the article specifically for queued TRIM? E.g. https://github.com/torvalds/linux/commit/9a9324d https://github.com/torvalds/linux/commit/9a9324d. SO either that blacklist has nothing to do with this issue (in which case it probably shouldn't be linked from the article), or it does, and we're talking about issues with queued TRIM.
- lolgay5 11y agoThe article very clearly states that the issue had nothing to do with queued or unqueued TRIM: Our affected drives did not match any pattern so they were implicitly allowed full operation. See the list: SAMSUNG MZ7WD480HCGM-00003 SAMSUNG MZ7GE480HMHP-00003 SAMSUNG MZ7GE240HMGR-00003