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.

I can reproduce the problem with mlocate-0.26-6.el7.x86_64 using these steps:

yum install -y mlocate btrfs-progs
modprobe scsi_debug dev_size_mb=40
mkfs.btrfs /dev/sda
mkdir bt
mount /dev/sda bt
btrfs subvolume create bt/root
btrfs subvolume create bt/home
umount bt
mount -o subvol=root /dev/sda bt
mkdir bt/home
mount -o subvol=home /dev/sda bt/home
touch bt/rootfile
touch bt/home/homefile
updatedb
locate rootfile
locate homefile

+++ This bug was initially created as a clone of Bug #906591 +++

Description of problem:
Files that I know exist in my home directory were not displayed by the locate command.

The problem was traced to updatedb not indexing /home, because it believes /home is a bind mount for some reason. Disabling the PRUNE_BIND_MOUNT option in /etc/updatedb.conf fixed the problem.
...

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.