Bug 1331874

Summary:	[RFE] Could we have gluster volume start ensure that individual bricks are included in /etc/updatedb.conf exclusions?
Product:	Red Hat Gluster Storage	Reporter:	Peter Portante <pportant>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-21 06:40:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Peter Portante 2016-04-29 21:07:18 UTC

Would it be possible to have gluster ensure that /etc/updatedb.conf contain all the disks participating as bricks in the /etc/updatedb.conf?  Or at least issue a warning to the user notifying them?

I almost had 3 of the 6 nodes in the cluster fill up their system disks with large updatedb databases.

Comment 2 Atin Mukherjee 2016-04-30 07:09:17 UTC

I think this has to be an admin's job or the utility which configures the brick mount points before they can be used by gluster volumes as glusterd refers to the brick path, not the underlying file system for its volume life cycle. Thoughts?