mysterious, hard drive intensive process after start up...
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Hardy (Gnome on Ubuntu 8.04) on Compaq N600c laptop
Posts: 323
Rep:
mysterious, hard drive intensive process after start up...
Hey all,
I have a fairly new and vanilla install of Etch on my laptop, and have chosen
JFS as the filesystem.
Not long after I boot up, say 2 minutes, some process will always start that provides no user interface whatsoever and works the hard drive pretty intensely for about 1-2 minutes.
Anyone know what this might be? A better question would be, how can I tell what process in general, at any given time, is tied to current disk activity (e.g. reads/writes, file opens, buffers, etc.)?
One possibility is the beagle daemon is indexing new files. Another is if a cron job checks if cron daily has been run in the last 24 hours and if not, starts it. That would run updatedb which would work the hard drive. Using ps and top as the previous poster recommended will tell you for sure.
Distribution: Hardy (Gnome on Ubuntu 8.04) on Compaq N600c laptop
Posts: 323
Original Poster
Rep:
How do I know which of the processes in either top or ps are associated with the the hdd activity? The CPU % in top isn't a good correlation with it; is one of the others more directly associated with media i/o?
I suspect that activity is because of cron. What happens is that Linux schedules some automated tasks (e.g. updatedb and log rotation) to be run at certain times of the day and if the computer is switched off at that time, the jobs are run whenever the computer is started. This sometimes makes the computer a little bit slow for a few minutes after initial startup, but things get back to normal once the jobs have finished.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.