LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   msec_find making system slow and thrashing hard drive once in a while (https://www.linuxquestions.org/questions/mandriva-30/msec_find-making-system-slow-and-thrashing-hard-drive-once-in-a-while-711327/)

k.king 03-13-2009 08:00 AM

msec_find making system slow and thrashing hard drive once in a while
 
actually running PCLOS MiniMe 2008 upgraded to PCLOS 2009 via Synaptic.
Since doing the upgrade I find generally once every day approx just after booting system gets unresponsive and hard drive is thrashed for a couple of minutes. The usage is never more than 15% and only for those couple of minutes. Is this normal for newer Mandriva/PCLOS ? It's the repeated thrashing of drive that worries me.

{BBI}Nexus{BBI} 03-14-2009 07:52 AM

Quote:

Originally Posted by k.king (Post 3474237)
actually running PCLOS MiniMe 2008 upgraded to PCLOS 2009 via Synaptic.
Since doing the upgrade I find generally once every day approx just after booting system gets unresponsive and hard drive is thrashed for a couple of minutes. The usage is never more than 15% and only for those couple of minutes. Is this normal for newer Mandriva/PCLOS ? It's the repeated thrashing of drive that worries me.

Firstly, PCLinuxOS is a fork of Mandriva you can't really compare the two in that way. They are completely separate distros. What happens in one doesn't always happen in the other.

Second, MiniMe is a very stripped down PCLinuxOS, now that you've upgraded to a full blown version of PClinux there will be things that happen now that never happened before.

Thirdly, the behavior of msec_find can be adjusted via Configure Your Computer--> Security--> Set up security level and audit.

I can't say I've noticed msec_find running after I boot up. It's usually ran at night time. Also, I didn't upgrade to 2009.

ernie 03-14-2009 11:56 AM

I use MDV 2009.0 (with KDE 4.2.1) and I do not notice this behaviour either

{BBI}Nexus{BBI} 03-14-2009 12:06 PM

Quote:

Originally Posted by ernie (Post 3475425)
I use MDV 2009.0 (with KDE 2.4.1)

Is this a typo..?

tux99 03-14-2009 02:47 PM

Quote:

Originally Posted by {BBI}Nexus{BBI} (Post 3475258)
I can't say I've noticed msec_find running after I boot up. It's usually ran at night time. Also, I didn't upgrade to 2009.

I would guess, PCLinuxOS uses 'anacron' to kick off cron jobs that should have run since the last shutdown, every time the PC gets started up.

Do a
Code:

chkconfig --list|grep -i anacron
on a console window to see if anacron is an active service.

ernie 03-14-2009 11:34 PM

Quote:

Originally Posted by {BBI}Nexus{BBI}
Is this a typo..?

No. I added (and installed KDE 4.2.1 from) the unofficial Mandriva repositories:
Code:

ftp://ftp.kde.org/pub/kde/stable/4.2.0/Mandriva/2009.0/RPMS/x86_64
ftp://ftp.kde.org/pub/kde/stable/4.2.0/Mandriva/2009.0/RPMS/noarch

or for 32 bit systems:
Code:

ftp://ftp.kde.org/pub/kde/stable/4.2.0/Mandriva/2009.0/RPMS/i586
ftp://ftp.kde.org/pub/kde/stable/4.2.0/Mandriva/2009.0/RPMS/noarch


{BBI}Nexus{BBI} 03-15-2009 09:12 AM

Quote:

Originally Posted by ernie (Post 3475824)
No. I added (and installed KDE 4.2.1 from) the unofficial Mandriva repositories

Yes it is a typo LOL. You put 2.4.1 in your previous post. I thought I was missing out on something, I'm also using the same repos as you. :)

{BBI}Nexus{BBI} 03-15-2009 09:20 AM

Quote:

Originally Posted by tux99 (Post 3475552)
I would guess, PCLinuxOS uses 'anacron' to kick off cron jobs that should have run since the last shutdown, every time the PC gets started up.

I agree, I noticed today when I booted up that: awk, msec_find & rpm* (* I can't remember if it was check or update) ran straight away. I wouldn't say they were 'thrashing' the drive though.

ernie 03-15-2009 10:45 PM

Quote:

Originally Posted by {BBI}Nexus{BBI}
Yes it is a typo LOL. You put 2.4.1 in your previous post. I thought I was missing out on something, I'm also using the same repos as you.

Good eye! I checked that post when I posted it, then again when you first asked about it and still did not catch my error. I fixed it now though - Thank You.

I use anacron here (because I often shut the system down when not in use) and I have not experienced any thrashing of my hard drive following system start. If you were using Windows I'd think you need to defragment the hard drive. Just out of curiosity, does fsck report any unusual fragmentation? (Note: I know, Linux usually does not suffer from such troubles . . . this is simply idle curiosity)

ism 03-16-2009 04:32 PM

Quote:

Originally Posted by k.king (Post 3474237)
actually running PCLOS MiniMe 2008 upgraded to PCLOS 2009 via Synaptic.
Since doing the upgrade I find generally once every day approx just after booting system gets unresponsive and hard drive is thrashed for a couple of minutes. The usage is never more than 15% and only for those couple of minutes. Is this normal for newer Mandriva/PCLOS ? It's the repeated thrashing of drive that worries me.

you have done well to run what you have got! - the guys at PCLinux are well meaning but could not organise - forgive my french - a "piss up in a brewery" maybe because linux is open source and so is accessible by anyone - and in this case they have a microshaft insider - they have had this problem before - a sign of respect from the powers that be... their os2007 was seriously good - good enough and reliable enough to trust - to make business with - i know - i did - but then it was 'micro'shafted - (that's why there was no 2008 os - only a half way house update)

my advice would be to shift to another distribution - until PCLinux find out (if they are even looking) who is buggering them up.

i am experimenting with fedora 11 x64 - it is crap compared to PCLinux2007 but at least it works, works with new hardware and upgrades ok. - unlike PCLinux

{BBI}Nexus{BBI} 03-16-2009 08:03 PM

Quote:

Originally Posted by ism (Post 3477539)
...the guys at PCLinux are well meaning but could not organise - forgive my french - a "piss up in a brewery"...

That's a bit harsh. They're not some big outfit, with the resources to do thorough testing. It's not like upgrading was the only option on the table.

I find it strange how you encourage the OP to jump ship, rather than stay and help troubleshoot/resolve any problems.

Upgrading with any distro is rarely trouble free. 2009 is just as reliable as 2007 from a fresh install (in my experience).

What's with all the reference to microshaft? Would you care to elaborate?

ernie 03-16-2009 10:56 PM

Sounds to me as if ism is the 'microshaft'-er here . . .

I agree. It is inappropriate to give any advise other than a proper solution to the problem posed. To suggest the OP abandon ship is just wrong. If all users of all distributions did that instead of finding solutions to problems Linux would probably not exist today (at east not as the state of the art OS we all know and love). Since I do not use PCLOS here, my best suggestion would be to go to the PCLinuxOS Forum and see if any one there can help (if they can, please post back here to inform others).

k.king 03-17-2009 03:27 PM

tux99
chkconfig --list | grep -i anacron

yielded
anacron 0 : off 1 : off 2 : on 3 : on 4 : on 5 : on 6 : off

the (only a little) "thrashing" seems to be once a day, just after the first boot for day.
If it's required then fine, I was (a) commenting that PCLOS2007 didn't seem to do it, and (b) if it wasn't required I wouldn't mind trying reduce the wear and tear on the hard disk.

ernie 03-17-2009 04:10 PM

In answer to (b) above: whether 'it' is required depends on specifically what 'it' is (e.g.: the software or service causing the 'thrashing' of the hard drive). If you can determine what is causing the trouble (may be run by anacron - or may not), you could try stopping it and see if anything changes (other than the 'thrashing'). If not, keep it stopped.

I do not use PCLinuxOS here (I'm a Mandriva user for more than a decade) and I do not know exactly which services (processes) run at boot time. If you have a desktop search service (perhaps beagle or something similar) installed, that could be the cause - many of these run in the background to update their catalogue at boot time.

HTH,


All times are GMT -5. The time now is 09:26 AM.