On Wed, 2021-08-18 at 21:51 -0500, Dave Ulrick wrote: > On 8/18/21 2:16 PM, Jan-Henrik Sorsimo via users wrote: > > > I see the same behavior since using a btrfs subvol for / > > > > > > Commenting PRUNE_BIND_MOUNTS = "yes" in /etc/updatedb.conf solves > > > this > > > problem. > > Indeed, that was it for me at least. Looks like the issue has been > > written about: > > > > https://pagure.io/mlocate/issue/36 > > https://lore.kernel.org/linux-btrfs/b5e7e64a-741c-baee-bc4d-cd51ca9b3a38@xxxxxxxxx/T/ > > > As the OP for this topic, I can confirm that commenting > PRUNE_BIND_MOUNTS = "yes" in /etc/updatedb.conf does solve the issue. It does. I made the change yesterday and the nightly run updated the database correctly. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
