md raid0 w/ fstrim causing data loss
Bug #1457510 reported by
Luis Henriques
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
High
|
Leann Ogasawara | ||
| Utopic |
Invalid
|
Undecided
|
Luis Henriques | ||
| Vivid |
Invalid
|
Undecided
|
Luis Henriques | ||
| Wily |
Invalid
|
High
|
Leann Ogasawara | ||
Bug Description
Commit 47d68979cc96 ("md/raid0: fix bug with chunksize not a power of 2.") introduced in v4.1 development has been picked by stable trees, and is causing issues (see https:/
This commit has been dropped from Vivid and Utopic when pulling the changes from stable trees 3.19.7 and 3.16.7-ckt11 respectively (bug #1454699 and bug #1454202).
The fix for this issue is not upstream yet, and should be picked by stable trees. Here's the link for the proposed fix: http://
break-fix: 47d68979cc96853
| Changed in linux (Ubuntu Vivid): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Utopic): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Vivid): | |
| assignee: | nobody → Luis Henriques (henrix) |
| Changed in linux (Ubuntu Utopic): | |
| assignee: | nobody → Luis Henriques (henrix) |
| Changed in linux (Ubuntu Wily): | |
| assignee: | Luis Henriques (henrix) → nobody |
| Changed in linux (Ubuntu Wily): | |
| assignee: | nobody → Leann Ogasawara (leannogasawara) |
| status: | Triaged → In Progress |
| importance: | Undecided → High |
| description: | updated |
| Changed in linux (Ubuntu Wily): | |
| status: | In Progress → Fix Committed |
| tags: | added: kernel-bug-break-fix |
| description: | updated |
| Changed in linux (Ubuntu Utopic): | |
| status: | Triaged → Invalid |
| Changed in linux (Ubuntu Vivid): | |
| status: | Triaged → Invalid |
| Changed in linux (Ubuntu Wily): | |
| status: | Fix Committed → Invalid |
| tags: | removed: kernel-bug-break-fix |
| tags: | added: kernel-bug-break-fix kernel-bug-break-fix-manual |
| Changed in linux (Ubuntu Utopic): | |
| status: | Invalid → New |
| Changed in linux (Ubuntu Vivid): | |
| status: | Invalid → New |
| Changed in linux (Ubuntu Wily): | |
| status: | Invalid → New |
| status: | New → Triaged |
| Changed in linux (Ubuntu Vivid): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Utopic): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Utopic): | |
| status: | Triaged → Invalid |
| Changed in linux (Ubuntu Vivid): | |
| status: | Triaged → Invalid |
| Changed in linux (Ubuntu Wily): | |
| status: | Triaged → Invalid |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in linux (Ubuntu Wily): | |
| status: | Invalid → Fix Released |
| Changed in linux (Ubuntu Wily): | |
| status: | Fix Released → Invalid |
| Changed in linux (Ubuntu): | |
| status: | Invalid → Fix Released |
To post a comment you must log in.
This bug was fixed in the package linux - 4.0.0-4.6
---------------
linux (4.0.0-4.6) wily; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1470233
* rebase to mainline v4.0.7
[ Jay Vosburgh ]
* SAUCE: fan: Proof of concept implementation (v2)
- LP: #1439706
* SAUCE: fan: tunnel multiple mapping mode (v3)
- LP: #1470091
[ Upstream Kernel Changes ]
* rebase to v4.0.7
- LP: #1427680
- LP: #1462614
-- Andy Whitcroft <email address hidden> Tue, 30 Jun 2015 16:55:32 +0100