[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: James Youngman
Subject: [bug #33207] updatedb (findutils-locate) has a memory leak on large nfs mounts, the index is not complete
Date: Sat, 14 May 2011 21:54:32 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10

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

I think it's unlikely that this problem is NFS-specific.   

Are you sure it is find which is consuming all the memory?   Not sort?   How
many files, in total, are involved?  (you can figure this out by running
locate -S on a correct database)

What is the command line of the find process which is using up all the
system's memory?   Do you get the same effect if you run the same find command
on the NFS server directly, with the local filesystem paths (I suppose you
will need to adjust the directory names)?

What is the newest findutils 4.4.x release which is not affected by this

Does a system call trace (with e.g. strace on Linux or its equivalent on the
NFS server) reveal any difference between the affected and unaffected
releases, or any otherwise interesting behaviour?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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