Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10532 - updatedb (mlocate) doesn't work correctly
Attached to Project:
Arch Linux
Opened by Lith (Lith) - Thursday, 29 May 2008, 13:15 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 18:36 GMT
Opened by Lith (Lith) - Thursday, 29 May 2008, 13:15 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 18:36 GMT
|
DetailsDescription:
When my system put update the database, this one doesn't work correctly, In fact, the CPU is at 100% and my computer is unuseable. Additional info: * package version(s) updatedb (mlocate) 0.18 Copyright (C) 2007 Red Hat, Inc. All rights reserved. This software is distributed under the GPL v.2. This program is provided with NO WARRANTY, to the extent permitted by law. * config and/or log files etc. Config : - Dell inspiron 640m - i686 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux Log file: /etc/updatedb.conf # directories to exclude from the slocate database: PRUNEPATHS="/tmp /var/tmp /usr/tmp /var/spool /var/cache" # filesystems to exclude from the slocate database: PRUNEFS="nfs smbfs ncpfs afs proc smbfs autofs auto iso9660 coda ftpfs cifs" -- Steps to reproduce: 1) # updatedb 2) You can see the CPU at 100% - the computer is slow and unuseable. -- Lith (user) |
This task depends upon
Then it just detects changes.
I have test many things.
Rebooting - reinstallation of mlocate...
But the problem is the same :(
The other difference to you is that i have "/media /mnt" in the PRUNEPATHS array but this could be only cosmetical for you.
I try this :
$ sudo nice -n 19 ionice -c 3 /usr/bin/updatedb
The CPU of my computer stay at 100 % during a very long moment... I've stopped manually "updatedb" because I can't use my computer and the update stay blocked.
The problem isn't repaired :(
To test it again i delete mlocate.db and recreate with less < 10% CPU:
time /etc/cron.hourly/updatedb
real 2m50.548s
user 0m0.358s
sys 0m5.730s
You can test it with only one directory as described at the end of the manpage. For example:
/usr/bin/updatedb -l 0 -o test.db -U /var/lib/pacman
I've installed the version 0.20 from "testing".
I've doing :
/usr/bin/updatedb -l 0 -o test.db -U /var/lib/pacman
This line running without problem !
But if I want locate all files, the problem is the same...
I think "updatedb" block on certain files... but I don't know exactly why and where...
Thanks for your help.
How long does "updatedb" take?
If you're system is idle, there's nothing wrong with it using 100% CPU... that's just the kernel scheduler doing its job. It's unresponsive bit that shouldnt be happening and is probably mlocate dominating hdd io.
edit: Random note, instead of using nice, use schedtools and set the task batch/idleprio.
Using schedtools is a nice option too.
I have test and now it's good !
I don't know exactly how this bug was repair.
If this bug is reproduced, I will give you how long exactly "updatedb" will.