trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fstrim (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Invalid
|
Undecided
|
Unassigned | ||
Utopic |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Dave Chiluk | ||
Utopic |
Fix Released
|
High
|
Dave Chiluk | ||
Vivid |
Fix Released
|
High
|
Dave Chiluk |
Bug Description
Hi,
after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and "bad sectors" reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command "sudo fstrim /" the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved.
Thanks
===
break-fix: - 6fc4d97a4987c5d
break-fix: - 9a9324d3969678d
Changed in fstrim (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in fstrim (Ubuntu Trusty): | |
status: | New → Invalid |
Changed in fstrim (Ubuntu Utopic): | |
status: | New → Invalid |
Changed in fstrim (Ubuntu Vivid): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
Changed in linux (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in linux (Ubuntu Utopic): | |
status: | New → Triaged |
Changed in linux (Ubuntu Vivid): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Utopic): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Vivid): | |
importance: | Undecided → High |
description: | updated |
tags: | added: kernel-bug-break-fix |
Changed in linux (Ubuntu Trusty): | |
status: | Triaged → Confirmed |
Changed in linux (Ubuntu Utopic): | |
status: | Triaged → Confirmed |
Changed in linux (Ubuntu Vivid): | |
status: | Triaged → Confirmed |
Changed in linux (Ubuntu): | |
status: | Triaged → Confirmed |
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Dave Chiluk (chiluk) |
Changed in linux (Ubuntu Utopic): | |
assignee: | nobody → Dave Chiluk (chiluk) |
Changed in linux (Ubuntu Vivid): | |
assignee: | nobody → Dave Chiluk (chiluk) |
Changed in linux (Ubuntu Vivid): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Trusty): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Utopic): | |
status: | Confirmed → Fix Committed |
tags: | added: verification-done-trusty verification-done-utopic |
tags: |
added: verification-done-vivid removed: verification-done-utopic |
tags: | added: verification-done-utopic |
Status changed to 'Confirmed' because the bug affects multiple users.