[LU-1124] Add lustre to /etc/updatedb.conf Created: 21/Feb/12  Updated: 20/Mar/14  Resolved: 20/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 1.8.x (1.8.0 - 1.8.5)
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Scott Barber Assignee: Andreas Dilger
Resolution: Fixed Votes: 0
Labels: updatedb
Environment:

Linux client 2.6.18-238.12.1.el5
lustre-client-1.8.6-wc1_2.6.18_238.12.1.el5 and lustre-client-modules-1.8.6-wc1_2.6.18_238.12.1.el5 RPMs installed


Severity: 3
Rank (Obsolete): 10318

 Description   

Please add "lustre" to PRUNEFS in /etc/updatedb.conf



 Comments   
Comment by Andreas Dilger [ 21/Feb/12 ]

Scott,
this is really an issue to bring up with your distribution provider. We submitted this exclusion to RHEL a long time ago (at least for RHEL4), but it seems that the original change was lost when moving from "slocate" to "mlocate", based on the "mlocate-0.15-1.el5.2.x86_64" package:

PRUNEFS = "auto afs gfs gfs2 iso9660 sfs udf"

Checking on my FC12 and FC13 test nodes this exception has been re-added since at least "mlocate-0.22.2-2.fc12.x86_64":

PRUNEFS = "9p afs anon_inodefs auto autofs bdev binfmt_misc cgroup cifs coda configfs cpuset debugfs devpts ecryptfs exofs fuse fusectl gfs gfs2 hugetlbfs inotifyfs iso9660 jffs2 lustre mqueue ncpfs nfs nfs4 nfsd pipefs proc ramfs rootfs rpc_pipefs securityfs selinuxfs sfs sockfs sysfs tmpfs ubifs udf usbfs"

In general, it is undesirable to install mlocate on compute nodes. I agree that for interactive login nodes that this still needs to be added to the PRUNEFS list, but this package is not under our control. I'd suggest to submit a bug to the upstream distro.

Comment by Scott Barber [ 21/Feb/12 ]

Andres,

I can file a bug report with the distro, but I'm wondering what the aversion is to doing it with the install of lustre itself? Maybe something simple like this? http://patches.gluster.com/patch/4415/

Comment by Andreas Dilger [ 20/Mar/14 ]

Have submitted patch to upstream mlocate a long time ago.

Generated at Sat Feb 10 01:13:43 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.