#53 Need to make locate / updatedb work on Btrfs subvolumes
Closed: Fixed by chrismurphy. Opened by salimma.

Fedora ships mlocate by default, with a modified configuration that skips indexing bind mounts (9 year old, unresolved bug report). This has been an issue for Silverblue before, and the fix was to modify the config post-install to turn this off on Silverblue and ostree-based installations: proposed fix, commit.

Now that Btrfs is the default on Workstation and other desktops (since F33) and Cloud (since F35), this is hitting a majority of new installations, as mlocate's updatedb sees mounted Btrfs subvolumes as ... bind mounts.

We should push to fix this properly rather than hacking an exception for ostree-based installations. We should also consider replacing mlocate with plocate which Debian uses by default, as discussed a few months ago in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/443KJWXU7CERMDBYYVRH3DDGWMLFQPY5/#INVZGADRHH5Q47ZJIDKHZIX6GOLJ2SIE


I'm pretty sure @zbyszek would be pleased to see this happen. Maybe you can work with him on a self-contained change for Fedora Linux 36?

Metadata Update from @ngompa:
- Issue assigned to salimma
- Issue set to the milestone: Fedora 36
- Issue tagged with: Cloud, Desktop, Server, Utils

Metadata Update from @ngompa:
- Issue tagged with: Dev

This change will fix the problem so I'll close this out even though it's not yet an approved change (it will be approved or I'll eat a billy goat)
https://fedoraproject.org/wiki/Changes/Plocate_as_the_default_locate_implementation
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WYS5LANEOA2W7MYCXDQDJTOMFOUZCYYK/

Metadata Update from @chrismurphy:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata