CONFIG_BLK_DEV_IO_TRACE is not enabled preventing blktrace from working
Bug #118303 reported by
Robert Collins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.22 (Debian) |
Fix Released
|
Unknown
|
|||
linux-source-2.6.22 (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.22
blktrace appears to be a useful program in many places, but it needs this option enabled to operate. Particularly I've seen reference to blktrace for debugging disk weirdness and performance profiling. I'd like to have the bzr devs be able to use it for performance tuning...
Changed in linux-source-2.6.22: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Wishlist |
status: | Unconfirmed → Confirmed |
Changed in linux-source-2.6.22: | |
status: | Unknown → New |
Changed in linux-source-2.6.22: | |
status: | Confirmed → Triaged |
Changed in linux-source-2.6.22: | |
status: | New → Fix Committed |
Changed in linux-source-2.6.22: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Adding "me too" for this. I have exhausted all attempts to find what system process is continuously writing (100% of the time) to my disk on my System76 laptop. Without blktrace working I am sunk. The problem started when I did a fresh install of Feisty so reinstalling won't fix the issue.