Bug 1845275 - nfs is still pruned if removed from /etc/updatedb.conf
Summary: nfs is still pruned if removed from /etc/updatedb.conf
Alias: None
Product: Fedora
Classification: Fedora
Component: mlocate
Version: 33
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michal Sekletar
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-06-08 19:36 UTC by René Lesterhuis
Modified: 2021-11-30 16:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2021-11-30 16:34:58 UTC
Type: Bug

Attachments (Terms of Use)

Description René Lesterhuis 2020-06-08 19:36:00 UTC
Description of problem:
When removing nfs* from the line PRUNEFS in the file /etc/updatedb.conf nfs mounts do not get indexed.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. mount an nfs share on a mount point not excluded by PRUNEPATHS in updatedb.conf
2. execute /usr/libexec/mlocate-run-updatedb
3. see if filenames on the nfs mount can be found with the locate utility

Actual results:
Files on the nfs mount can not be found with the locate utility

Expected results:
Files on the nfs mount can be found with the locate utility

Additional info:
The problem is created by the /usr/libexec/mlocate-run-updatedb script. In this script there is a variable nodevs defined in a way that nfs* gets included and then updatedb is run with these extra entries in nodevs.
As a work around i change the line
nodevs=$(< /proc/filesystems awk '$1 == "nodev" && $2 != "rootfs" && $2 != "zfs" { print $2 }')
nodevs=$(< /proc/filesystems awk '$1 == "nodev" && $2 != "rootfs" && $2 != "zfs" && $2 !~ "nfs" { print $2 }')

I also noticed the URL in the package is poiting to an old website:
$ rpm -qi mlocate | grep ^URL
URL         : https://fedorahosted.org/mlocate/
Please update.

Comment 1 Ben Cotton 2021-11-04 17:22:12 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-11-30 16:34:58 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.