Bug 1331874 - [RFE] Could we have gluster volume start ensure that individual bricks are included in /etc/updatedb.conf exclusions?
Summary: [RFE] Could we have gluster volume start ensure that individual bricks are in...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-29 21:07 UTC by Peter Portante
Modified: 2017-12-21 06:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-21 06:40:38 UTC
Target Upstream Version:

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

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?
Note You need to log in before you can comment on or make changes to this bug.