lm-profiler: non-informational output with raid systems

[ceg]

Binary package hint: laptop-mode-tools

When the filesystem is on a raid device, lm-profiler only reports disk access by a process called md0_raid1 (the md module).

Unfortunately, this information does not help in identifying the processes that actually causes the disk access.

[Ritesh Raj Sarraf (rrs)]

On 03/17/2011 10:57 PM, ceg wrote:
> ** Also affects: laptop-mode-tools
> Importance: Undecided
> Status: New
>
Does this help?
http://mailman.samwel.tk/pipermail/laptop-mode/2009-May/000103.html

--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[ceg (ceg)]

Thank you for the link.

I found out about block_dump, and unfortunately, that laptop_mode seems to gets into a resyncing loop with raid devices.
Hopefully, has there bin some progress in resolving that?

Concerning the bug reported, maybe lm-profiler could look at the writes to the md or lvm devices as well as to the physical devices?

[Ritesh Raj Sarraf (rrs)]

On 03/18/2011 06:13 PM, ceg wrote:
> I found out about block_dump, and unfortunately, that laptop_mode seems to gets into a resyncing loop with raid devices.
> Hopefully, has there bin some progress in resolving that?
>
> Concerning the bug reported, maybe lm-profiler could look at the writes
> to the md or lvm devices as well as to the physical devices?
I'm not sure but I think we just make use of what the kernel provides.
I'll still check though.

--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."