Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
RFE Request by Customer.
- It is regarding disabling the by default indexing feature of updatedb.
- In the /etc/updatedb.conf we have a parameter "PRUNEFS=" in which we define the filesystems and subfilesystems(fuse.sshfs, here referring sshfs as subfilesystem) on which we want to disable the indexing of updated, if I am not wrong.
- Customer wants to disable indexing on all the subfilesystems for by default, for now customer has to manually mention that subfilesystem in the "PRUNEFS=", for the instance: fuse.sshfs or fuse.gvfs.
- Customer has pointed our an upstream patch for this: https://fedorahosted.org/mlocate/ticket/34
I asked for the business justification from the custpomer and below is his response on that:
Thanks Madhur. The business justification is that currently, nearly all
fuse filesystems use a filesystem subtype to indicate what particular type
of filesystem they are. This is an extremely useful feature. However, it
also breaks the filesystem detection logic in updatedb because updatedb
looks for the exact strings in PRUNEFS. This makes the PRUNEFS=fuse
setting in updatedb counter-intuitive and useless.
Making the change would allow updatedb to work as expected out of the box
without needing further tweaking by administrators. This eliminates the
debugging needed when presented by mysterious filesystem traffic, which
originates from updatedb, saving the organization money in terms of
administrator time and lost productivity due to over-burndened
filesystems.
I granted this bug devel_ack+ by mistake. I was under the impression that patch mentioned in bug description was already merged upstream and this is just a backport request. However, this is not the case.
I agree with the proposed solution, on the other hand, I think that doing this change in RHEL is risky. Change in default behavior must be first merged upstream.
Comment 12RHEL Program Management
2020-12-15 07:45:38 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.