I have something that is poling my hard drive about every two seconds. It’s really not necessary I don’t think. I am not sure how to find out what process it is. My memory usage is pretty low and I am not using any swap.
How do I go about tracking the culprit down?
KDE 4.4 11.3 latest kernel.
I normally run the System Monitor (ksysguard, from KDE) to track down the culprit, but suspects are Tracker (You can search YaST / Software Management for this one) and Nepomuk (Enabled in KDE Personnel Settings for Desktop Search). I normally uninstall Tracker if it is Loaded and disable Nepomuk if you use the KDE desktop. If not these, then perhaps the System monitor will tell the story.
Thank You,
Check the I/O usage with
iotop
On Tue, 19 Oct 2010 05:36:01 +0530, jdmcdaniel3
<jdmcdaniel3@no-mx.forums.opensuse.org> wrote:
> I normally run the System Monitor (ksysguard, from KDE) to track down
> the culprit, but suspects are Tracker (You can search YaST / Software
> Management for this one) and Nepomuk (Enabled in KDE Personnel Settings
> for Desktop Search). I normally uninstall Tracker if it is Loaded and
> disable Nepomuk if you use the KDE desktop. If not these, then perhaps
> the System monitor will tell the story.
i often find top or htop more accurate than ksysguard. but at times i
notice unusual high CPU load in plasma’s “system load viewer” applet (KDE
4.5.2, factory), but ksysguard shows only very little CPU use. starting
htop in a terminal however pins down the process.
recently i found nepomukservice/file watcher getting stuck with 100% of
one CPU; when i killed the process it re-started and used only very little
CPU. that may be because i’m using KDE factory, which is a little more in
flux, of course. but i’ve noticed this earlier too, before switching to
factory again, that processes belonging to not fully stable services like
nepomuk & co need killing once in a while.
–
phani.
htop and iotop do not seem to be installed. top doesn’t show any process that coincides with the disk activity light. Just a glimpse frozen in time.
44 root 20 0 0 0 0 S 0 0.0 1:00.45 kondemand/3
3201 flamebai 20 0 254m 28m 14m S 0 0.7 23:58.38 xchat
12065 flamebai 20 0 373m 27m 15m S 0 0.7 0:00.32 konsole
17394 flamebai 20 0 707m 170m 32m S 0 4.3 7:31.27 firefox
1 root 20 0 12408 764 616 S 0 0.0 0:02.67 init
2 root 20 0 0 0 0 S 0 0.0 0:00.00 kthreadd
3 root RT 0 0 0 0 S 0 0.0 0:00.21 migration/0
4 root 20 0 0 0 0 S 0 0.0 0:06.47 ksoftirqd/0
5 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/0
6 root RT 0 0 0 0 S 0 0.0 0:00.21 migration/1
7 root 20 0 0 0 0 S 0 0.0 0:04.88 ksoftirqd/1
8 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/1
9 root RT 0 0 0 0 S 0 0.0 0:00.18 migration/2
10 root 20 0 0 0 0 S 0 0.0 0:03.82 ksoftirqd/2
11 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/2
12 root RT 0 0 0 0 S 0 0.0 0:00.10 migration/3
13 root 20 0 0 0 0 S 0 0.0 0:05.87 ksoftirqd/3
14 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/3
15 root 20 0 0 0 0 S 0 0.0 0:09.26 events/0
16 root 20 0 0 0 0 S 0 0.0 0:08.53 events/1
17 root 20 0 0 0 0 S 0 0.0 0:08.96 events/2
18 root 20 0 0 0 0 S 0 0.0 0:13.39 events/3
19 root 20 0 0 0 0 S 0 0.0 0:00.00 netns
20 root 20 0 0 0 0 S 0 0.0 0:00.00 async/mgr
21 root 20 0 0 0 0 S 0 0.0 0:00.00 pm
22 root 20 0 0 0 0 S 0 0.0 0:00.35 sync_supers
23 root 20 0 0 0 0 S 0 0.0 0:00.44 bdi-default
24 root 20 0 0 0 0 S 0 0.0 0:00.00 kintegrityd/0
25 root 20 0 0 0 0 S 0 0.0 0:00.00 kintegrityd/1
26 root 20 0 0 0 0 S 0 0.0 0:00.00 kintegrityd/2
27 root 20 0 0 0 0 S 0 0.0 0:00.00 kintegrityd/3
28 root 20 0 0 0 0 S 0 0.0 0:00.87 kblockd/0
29 root 20 0 0 0 0 S 0 0.0 0:00.21 kblockd/1
30 root 20 0 0 0 0 S 0 0.0 0:00.18 kblockd/2
31 root 20 0 0 0 0 S 0 0.0 0:00.08 kblockd/3
32 root 20 0 0 0 0 S 0 0.0 0:00.00 kacpid
33 root 20 0 0 0 0 S 0 0.0 0:00.00 kacpi_notify
34 root 20 0 0 0 0 S 0 0.0 0:00.00 kacpi_hotplug
35 root 20 0 0 0 0 S 0 0.0 0:00.02 khubd
36 root 20 0 0 0 0 S 0 0.0 0:00.00 kseriod
41 root 20 0 0 0 0 S 0 0.0 2:02.55 kondemand/0
42 root 20 0 0 0 0 S 0 0.0 1:44.11 kondemand/1
43 root 20 0 0 0 0 S 0 0.0 1:15.92 kondemand/2
78 root 20 0 0 0 0 S 0 0.0 0:00.00 khelper
Nepomuk is already off 
and Tracker is not installed.
On Tue, 19 Oct 2010 05:36:01 +0530, jdmcdaniel3
<jdmcdaniel3@no-mx.forums.opensuse.org> wrote:
> I normally run the System Monitor (ksysguard, from KDE) to track down
> the culprit, but suspects are Tracker (You can search YaST / Software
> Management for this one) and Nepomuk (Enabled in KDE Personnel Settings
> for Desktop Search). I normally uninstall Tracker if it is Loaded and
> disable Nepomuk if you use the KDE desktop. If not these, then perhaps
> the System monitor will tell the story.
i often find top or htop more accurate than ksysguard. but at times i
notice unusual high CPU load in plasma’s “system load viewer” applet (KDE
4.5.2, factory), but ksysguard shows only very little CPU use. starting
htop in a terminal however pins down the process.
recently i found nepomukservice/file watcher getting stuck with 100% of
one CPU; when i killed the process it re-started and used only very little
CPU. that may be because i’m using KDE factory, which is a little more in
flux, of course. but i’ve noticed this earlier too, before switching to
factory again, that processes belonging to not fully stable services like
nepomuk & co need killing once in a while.
–
phani.
htop and iotop do not seem to be installed.
zypper in htop iotop
FlameBait wrote:
> htop and iotop do not seem to be installed.
i think both are easily installed from the standard repo…
–
DenverD
When it comes to chocolate, resistance is futile.
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
I got htop and iotop installed and have run them I really don’t see any obvious culprit. This might be one of those “it can’t be helped” things. I do have six hard drives installed.
sdc is my / and /home and a process jbd2/sdc1-8 and jbs2/sdc2-8 does show up a lot in iotop