The information Chris needs is the command name, which is the far right
column. PIDs are an arbitrary identifier, except for 1 which is always
the init process.
If you have the screenshot, I recommend visiting the bug in launchpad
and attaching it to a comment. Email replies to bugs do not add
Harvey is right - process names would be more useful. However, if those
numbers are the highest numbers, then there isn;t a lot of disk activity
going on here at all. The numbers are very low.
I'm not sure whether iotop shows disk activity from memory management
tasks such as swapping, and I
Right, I've checked at home and iotop does show things like swapping.
With the information presented here so far, there isn't really any
evidence of excessive disk activity at all.
Could you please still provide the output of 'free -m'. In addition,
could you attach the following to this bug
Chris,
Don has isolated the flashing drive led, to his removable CD-RW device.
Based on his response in the related question, I do not think he will be
responding to the bug. Therefore you can probably close the bug, or
just let it expire.
Best regards,
Harvey
--
constant disk access
Harvey,
Thanks for assisting Don in Answer #38043. As this is no longer a
problem, I will mark this bug Invalid.
Thank you
** Changed in: ubuntu
Status: Incomplete = Invalid
--
constant disk access
https://bugs.launchpad.net/bugs/245022
You received this bug notification because you
Thank you for taking the time to report this bug and make Ubuntu better.
We need to try and determine what process is using your hard disk. To do
this, could you please try running 'iotop' from the terminal and report
back which processes are using the most disk I/O? Iotop is not installed
by
Hi Chris,
I found: PID 5458 donde 78.63 K/s write
PID 2442 root 22.90 K/s write
Both flashed by very fast, not at same time. PID 2442 seemed most frequent.
Did repeated check, using Snapshot application to capture. The iotop
program should have a way to capture
