Comment 14 for bug 560237

Michael,
I used iotop and found that I have 2 instances of kjournald running, which both are doing a lot(!) of disk access. I also saw "rsyslogd -c4" which also does a lot of disk access. The latter probably was due to another failed upgrade part, namely mythtv is solidly broken by the upgrade. The mythbackend perpetually terminates and respawns, which may be creating much/most/all of this logging activity:
...
Apr 15 19:38:06 athlon--80gb init: mythtv-backend main process (6014) terminated with status 254
Apr 15 19:38:06 athlon--80gb init: mythtv-backend main process ended, respawning
Apr 15 19:38:11 athlon--80gb init: mythtv-backend main process (6020) terminated with status 254
Apr 15 19:38:11 athlon--80gb init: mythtv-backend main process ended, respawning
Apr 15 19:38:16 athlon--80gb init: mythtv-backend main process (6026) terminated with status 254
Apr 15 19:38:16 athlon--80gb init: mythtv-backend main process ended, respawning
Apr 15 19:38:21 athlon--80gb init: mythtv-backend main process (6037) terminated with status 254
Apr 15 19:38:21 athlon--80gb init: mythtv-backend main process ended, respawning
...
killing the mythbackend brought some peace

I still have these network outgoing bursts every 3 second. Is there something like iotop for network ('nettop') to see which programs are doing this?