[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #33207] updatedb (findutils-locate) has a memory leak on large nfs

From: anonymous
Subject: [bug #33207] updatedb (findutils-locate) has a memory leak on large nfs mounts, the index is not complete
Date: Sat, 14 May 2011 22:58:36 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20110420 SUSE/3.6.17-0.2.1 Firefox/3.6.17

Follow-up Comment #2, bug #33207 (project findutils):

a: May be the nfs-shares cause only the big amount.

b: Yes, I used "top" (mem-sorted) - "find" was the first, not sort.

Here is the output(good case):

LANG=C locate -S
Database /var/lib/locatedb is in the GNU LOCATE02 format.
Locate database size: 894160900 bytes
All Filenames: 76872632
File names have a cumulative length of 6408432554 bytes.
Of those file names,

        3809128 contain whitespace, 
        35 contain newline characters, 
        and 245038 contain characters with the high bit set.
Compression ratio 86.05% (higher is better)

c: the command line for find was created by the cronjob-script(made by you or
by opensuse).
I will deliver it later, hoping the ps-command will not cutting it.

The nfs-shares are mounted from different servers. 

d: A quite old system with 4.4.0 works. I have no versions between.

My experience with strace is very poor. I afraid the file will be very big and
my conclusions will be very small. I give it a try within the next days.



Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]