From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.3) Gecko/20010801
Description of problem:
My Presario 1655's harddrive constantly runs (constant disk access and
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: harddrive constantly thrashes
Expected Results: Disk access when needed and not constantly.
Is this different compared to previous releases ?
i have the same problem.
this is not different from the previous release but i think you should do
my laptop has 256Mb memory and linux never let's it spin down.
even if you don't do anything on a computer linux accesses the harddrive
periodically for a very short time.
i think you should do something about this, because it's a big pain using linux
on a latop
I didn't recall having the same problem in 7.1, but not really sure.
I am having this problem as well. I am running RetHap 7.2 on a Dell Inspiron
7500. I didn't have this problem when the machine was running 6.2
I think it would help if y'all would check a few things:
- Check the cron tables for ~all~ the users on the system. "tail /var/log/cron" and see
who/what are running them.
- If you're a KDE user, turn off the .kde/Autostart/ Autorun entry which will poll often and show
HD access. If you're GNOME, consider turning off the equivalent thing that looks for new
media... I don't recall the 'magic' thing or whatever it is.
- Some X savers will hit disk constantly while they're running, not sure why. Turn the saver to
a blank screen, and this goes away.
I've seen this behavior on some IBM laptops since 7.2 even after turning off everything.
Literally dropping out of X (to prevent font rereading, etc.), chkconfig off most everything...
pretty raw system. Then eventually I noticed the same thing happened under Windows.. same
timing and such.
If you're drive is constantly thrashing it sounds like swapping for no reason or silly polling done
my Autorun or equiv. And it's probably not 'thrashing', just annoying. ;-)
If you really think there is an individual compontent causing this then consider doing the same
thing I did the first time around (after disabling the above):
- Drop out of X completely, shut it down. If that stopped the disk access, start comparing ps
-ef differences. Kill one process at a time, etc.
- Drink beer.
Also the "noatime" mount option is appropriate for laptops
Not a bug however