CONFIG_BLK_DEV_IO_TRACE is not enabled preventing blktrace from working

[Robert Collins]

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...

[Joey Stanford (joey)]

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.

[Jeff Schroeder (sejeff)]

For troubleshooting the top offenders for disk access, iotop would be really nice:
http://guichaz.free.fr/misc/

It requires CONFIG_BLK_DEV_IO_TRACE. Why can't this be in the gutsy kernel?

[Andy Price (andy-price)]

I'd like to add my (self-centered) "me too" also. I need CONFIG_BLK_DEV_IO_TRACE to be enabled in order to work on my computer science degree project. Fedora uses this option so I'll be booting into fedora to avoid the hassle of recompiling the kernel until it's enabled in Ubuntu. Apologies if my comment is unnecessary noise.

[Paul Sladen (sladen)]

Googling around, apparently this might used to have worked pre-Feisty and perhaps got dropped.

Disk I/O debugging is a bit ...impossible ...without CONFIG_BLK_DEV_IO_TRACE in there.

[Paul Sladen (sladen)]

<BenC> sladen: enabled and pushed for next upload

[Leann Ogasawara (leannogasawara)]

Looks like the config option was indeed enabled. Marking report as 'Fix Released'. Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.