Bug 674635 - slocate indexing
Summary: slocate indexing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: slocate
Version: 14
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-02 18:43 UTC by Chuck Wolber
Modified: 2013-01-10 06:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-04 20:32:48 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Chuck Wolber 2011-02-02 18:43:40 UTC 
Description of problem:

slocate attempts to index drives mounted to /mnt. This bit us when we mounted two 2TB drives to directories underneath /mnt and used them as local backup drives to supplement our remote backups.

PRUNEPATHS in /etc/updatedb.conf should have /mnt added to it.
Comment 1 Miloslav Trmač 2011-02-03 20:21:55 UTC 
Thaks for your report.

slocate has not been shipped in Fedora for several years.  Is this related to mlocate?

As for excluding /mnt, does indexing /mnt cause any actual problem?
Comment 2 Chuck Wolber 2011-02-03 21:35:57 UTC 
Yes, indexing /mnt causes actual problems. See the example I gave - It can be a bit of an issue when you index temporary storage, especially when it is 4TB of temporary storage. The indexing takes days, and several index jobs start backing up. This is a very real problem.
Comment 3 Miloslav Trmač 2011-02-04 17:47:14 UTC 
Fair enough, the FHS wording also suggests that indexing /mnt probably does not make sense.

/mnt will be excluded in rawhide mlocate-0.23.1-3.fc15, I'd rather not push such a functionality change into F14.
Note You need to log in before you can comment on or make changes to this bug.