[SOLVED] 22.04 base test - mlocate not working?

[oshunluvr]

The mlocate functions - updatedb and locate - appear to do nothing.

Can anyone confirm before I file a bug?

[claydoh]

notabug, well at least I think so, assuming that plocate is working correctly.
An Ubuntu bug if you had mlocate installed, and you didn't get plocate pulled in?

Ubuntu inherits Debian's switch to plocate
https://lwn.net/Articles/846405/
https://packages.ubuntu.com/jammy/mlocate
https://bugs.launchpad.net/ubuntu/+s...e/+bug/1960864

It is in the release notes for 22.04, and not even buried in the changelogs
https://discourse.ubuntu.com/t/jammy...se-notes/24668

[oshunluvr]

OK, but it's not working here.

[oshunluvr]

updatedb is still supposed to work as far as I can tell. It's not here...

[oshunluvr]

sudo updatedb -v (verbose) has zero results.

[jlittle]

IIRC the default configuration for updatedb has PRUNE_BIND_MOUNTS="yes", and updatedb sees btrfs subvolume mounts as bind mounts. I suggest checking /etc/updatedb.conf.

I've had to set PRUNE_BIND_MOUNTS to "no", and add lots of paths to PRUNEPATHS. In particular, .snapshots directories, that get hourly snapshots, would balloon the database to several hundred MB.

[oshunluvr]

Is this a change in 22.04? I've had " PRUNE_BIND_MOUNTS="yes" since 18.04 and never had this issue.

[oshunluvr]

My current updatedb.conf:

PRUNE_BIND_MOUNTS="yes"
# PRUNENAMES=".git .bzr .hg .svn"
PRUNEPATHS="/tmp /var/spool /media /var/lib/os-prober /var/lib/ceph /home/.ecryptfs /var/lib/schroot"
PRUNEFS="NFS afs autofs binfmt_misc ceph cgroup cgroup2 cifs coda configfs curlftpfs debugfs devfs devpts devtmpfs ecryptfs ftpfs fuse.ceph fuse.cryfs fuse.encfs fuscfs ocfs2 proc pstore rpc_pipefs securityfs shfs smbfs sysfs tmpfs tracefs udev udf usbfs"

From the Arch wiki:

PRUNE_BIND_MOUNTS
One of the strings 0, no, 1 or yes. If PRUNE_BIND_MOUNTS is 1 or yes, bind mounts are not scanned by updatedb(8). All file systems mounted in the subtree of a bind mount are skipped as well,
even if they are not bind mounts. As an exception, bind mounts of a directory on itself are not skipped. Note that Btrfs subvolume mounts are handled internally in the kernel as bind mounts
(see btrfs-subvolume(8)), and thus, may get skipped if you have also mounted the filesystem root itself. To counteract this, make your root directory a Btrfs subvolume, too.
By default, bind mounts are not skipped.

So since I do have my root filesystem mounted, this must be the issue. Thanks for the hint., working on it now

[oshunluvr]

That was it. Some re-working of the config put it back in order.