Bug 674635

Summary:	slocate indexing
Product:	[Fedora] Fedora	Reporter:	Chuck Wolber <chuckw>
Component:	slocate	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14	CC:	chuckw, dcantrell
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-04 20:32:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.