Investigate/Backport XFS Write Barrier fixes from 2.6.17
Bug #49083 reported by
John Dong
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-source-2.6.15 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Since 2.6.15, some fixes have been added to XFS's write barrier support to prevent it from sending filesystems into read-only for no good reason.
These fixes, which are in 2.6.17, also mean that XFS now has write barriers turned on by default. This in turn eliminates the instances of XFS corruption on hard resets that are caused by write caches.
I believe this is important enough for Dapper that it would be worth the effort to identify and backport these fixes in a Dapper kernel update, as it significantly benefits filesystem integrity in an environment with unstable power.
Revision history for this message
| Johnathon (kirrus) wrote | #1 |
| Changed in linux-source-2.6.15: | |
| status: | Unconfirmed → Rejected |
To post a comment you must log in.
Thanks for the bug report. I'm closing it because the bug has been fixed in a later version of ubuntu. Please please follow the instructions for "How to request new packages". <https:/