Bug 762270 (GLUSTER-538)

Summary: disable glusterfs mount from updatedb.conf
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: buildAssignee: Sachidananda Urs <sac>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: mainlineCC: fharshav, gluster-bugs, pavan, vijay, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1234385 (view as bug list) Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Amar Tumballi 2010-01-12 22:28:29 UTC 
either we have to add mount path in updatedb.conf, or disable glusterfs type from it (later is better), when we install glusterfs package.

Generally, updatedb.conf contains below entries.

amar@supernova:~/work/specs/unittest$ cat /etc/updatedb.conf 
PRUNE_BIND_MOUNTS="yes"
# PRUNENAMES=".git .bzr .hg .svn"
PRUNEPATHS="/tmp /var/spool /media"
PRUNEFS="NFS nfs nfs4 rpc_pipefs afs binfmt_misc proc smbfs autofs iso9660 ncpfs coda devpts ftpfs devfs mfs shfs sysfs cifs lustre_lite tmpfs usbfs udf"
----


We can add 'fuse.glusterfs' in PRUNEFS variable.. (because during install won't be knowing the path), or we have to have path editing script in mount.glusterfs only.


This is very critical for the performance for glusterfs mounts, as most of the linux installations configure mlocate to update every day, and it will create huge load on filesystem (mainly on glusterfs) when the number of files grow.

We can ask user to edit the files, but surely is not fool proof, instead we can get the scripts do it for them.
Comment 1 Vijay Bellur 2010-08-31 11:44:09 UTC 
PATCH: http://patches.gluster.com/patch/4415 in master (Add fuse.glusterfs to PRUNEFS variable in updatedb.conf(5))