Bug#1006906: plocate: cifs file system not being indexed by plocate or mlocate

[Ed Biow]

Package: plocate
Version: 1.1.13-1~bpo11+1
Severity: normal
X-Debbugs-Cc: edmun...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?

I noticed that the locate command is not indexing files on my local samba
server, which is where the vast majority of my files exist. My server mounts
from the fstab automatically, the entry in /proc/mounts is something like this:
//server/share /mnt/server cifs
rw,relatime,vers=3.1.1,cache=strict,username=USERNAMe,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.223.169,file_mode=0777,dir_mode=0777,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1
0 0
I always change the /etc/updatedb.conf file to remove cifs from PRUNEFS. The
command works as expected on my Ubuntu systems, mostly 20.04 using the
0.26-3ubuntu3 of mlocate. In the past mlocate worked on Debian.
The locate command is pretty useless to me without indexing my cifs directory.


* What exactly did you do (or not do) that was effective (or
ineffective)?
I repeatedly purged mlocate & plocate and tried different versions of mlocate
and plocate, both the standard bullseye stable version and the bullseye-
backports versions. I updated my updatedb.conf file and ran updatedb, but the
programs failed to index my server. The mlocate versions I tried were
1.1.13-1~bpo11+1 100 & 0.26-5. The plocate version I currently have installed
is the backports 1.1.13-1~bpo11+1, but I also tried the main repository
1.1.8-2+deb11u1 version. I also tried setting a new temporary 'updatedb' with
the command "updatedb -o /tmp/plocate.db" and searched it with 'locate -d
/tmp/plocate.db' but still couldn't see files on my server.


* What was the outcome of this action?

No joy. locate only dredges up files stored on my local computer.

* What outcome did you expect instead?

I expected updatedb to index my cifs share on my server as it has in the past.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plocate depends on:
ii libc6 2.31-13+deb11u2
ii libgcc-s1 10.2.1-6
ii libstdc++6 10.2.1-6
ii liburing1 0.7-3
ii libzstd1 1.4.8+dfsg-2.1

plocate recommends no packages.

Versions of packages plocate suggests:
ii systemd-sysv 247.3-6

-- Configuration Files:
/etc/updatedb.conf changed:
PRUNE_BIND_MOUNTS="yes"
PRUNEPATHS="/tmp /var/spool /media /var/lib/os-prober /var/lib/ceph"
PRUNEFS="NFS afs autofs binfmt_misc ceph cgroup cgroup2 coda configfs
curlftpfs debugfs devfs devpts devtmpfs ecryptfs ftpfs fuse.ceph fuse.glusterfs
fuse.gvfsd-fuse fuse.mfs fuse.rclone fuse.rozofs fuse.sshfs fusectl hugetlbfs
iso9660 lustre lustre_lite mfs mqueue ncpfs nfs nfs4 ocfs ocfs2 proc pstore
rpc_pipefs securityfs shfs sysfs tmpfs tracefs udev udf usbfs"

[Steinar H. Gunderson]

On Mon, Mar 07, 2022 at 05:12:47PM -0800, Ed Biow wrote:
> I always change the /etc/updatedb.conf file to remove cifs from PRUNEFS. The
> command works as expected on my Ubuntu systems, mostly 20.04 using the
> 0.26-3ubuntu3 of mlocate. In the past mlocate worked on Debian.
> The locate command is pretty useless to me without indexing my cifs directory.

There is a flag --debug-pruning to updatedb; could you add it and see whether
it gives any useful information?

/* Steinar */
--
Homepage: https://www.sesse.net/

[Edmund Biow]

Thank you for the suggestion. I noticed that the output of updatedb
mentioned my server as cifs, which is how it is mounted, but also as
"type 'autofs'", which I didn't have installed, so I didn't consider it.
I removed autofs from the PRUNEFS= line, ran updatedb again, and plocate
worked as expected. Thanks again.

[Steinar H. Gunderson]

On Wed, Mar 09, 2022 at 04:03:01PM -0800, Edmund Biow wrote:
> Thank you for the suggestion. I noticed that the output of updatedb
> mentioned my server as cifs, which is how it is mounted, but also as "type
> 'autofs'", which I didn't have installed, so I didn't consider it. I removed
> autofs from the PRUNEFS= line, ran updatedb again, and plocate worked as
> expected. Thanks again.

That's odd, but it's not something updatedb should try to invent on its own.
Does /proc/mounts say it is mounted as autofs?

[Edmund Biow]

Apparently.

grep autofs /proc/mounts 

systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=0,mi
nproto=5,maxproto=5,direct,pipe_ino=12584 0 0
systemd-1 /mnt/SERVER autofs rw,relatime,fd=54,pgrp=1,timeout=0,minproto=5,maxpro
to=5,direct,pipe_ino=12678 0 0

But autofs isn't installed, though on at least one system I remember installing autofs at one time to play around with it.

apt-cache policy autofs
autofs:
 Installed: (none)
 Candidate: 5.1.7-1
 Version table:
    5.1.7-1 500

As I mentioned /proc/mounts also reports my server mounted as cifs.