This bug seems to be related to a kernel change which was fixed for the
Questing kernel.
This bug should not be affecting Noble, because the kernel change was not
introduced there, and should not be affecting Questing, which has the new
kernel version with the fix.
I decided to re-verify the behavior to make sure of the current state.
I tested it by:
- launching a VM for those releases
- installing both iotop and iotop-c
- checking iotop-py -o output
- checking iotop-c -o output
- starting some IO heavy process (I used cp /dev/random ./file &)
- checking iotop-py -o output
- checking iotop-c -o output
On Noble and Questing, iotop-c and iotop-py both show the output
correctly. Before the heavy IO operation, the output is empty (except
from small read/write operations blinking). During the IO heavy
operation, it is constantly listed in the output and the IO values are
being shown.
On Plucky, iotop-c still works as expected and iotop-py is still
affected by this bug.
I am marking it invalid for iotop-py (iotop) on devel and Noble.
I am marking it invalid for iotop-c on all releases (someone with permissions
can remove the task I guess)
** Changed in: iotop-c (Ubuntu)
Status: Fix Released => Invalid
** Changed in: iotop-c (Ubuntu Noble)
Status: Triaged => Invalid
** Changed in: iotop-c (Ubuntu Plucky)
Status: Triaged => Invalid
** Changed in: iotop (Ubuntu Noble)
Status: Triaged => Invalid
** Changed in: iotop (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111673
Title:
iotop-py does not show IO values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/2111673/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
