Your message dated Wed, 20 Jul 2022 08:42:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#1015731: plocate database gaps after upgrade from
mlocate
has caused the Debian Bug report #1015731,
regarding plocate database gaps after upgrade from mlocate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1015731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015731
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: plocate
Version: 1.1.8-2+deb11u1
Severity: normal
X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
ORIGINAL PROBLEM
I was using mlocate 0.26-5, but it was missing files on btrfs partitions.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746943 describes the problem
and ends with an apparent suggestion to try plocate.
PLOCATE PROBLEM
I installed plocate; during installation it gave messages suggesting it was
doing a scan, although it seemed awfully quick.
After I ran locate, and again it missed directories it should have found:
locate -r "/\.hg$"
DIAGNOSIS
updatedb --debug-pruning -U /root -o test-plocate.db
/root/btr02, a mount of the root of the btrfs file system, appears not to be
excluded, which is good.
locate -d test-plocate.db -r "/\.hg$"
now correctly recovers lots of .hg directories under btr02.
POSSIBLE RECOVERY STRATEGIES
1. Maybe if I wait for the next daily update things will be OK.
2. Delete /var/lib/plocate/plocate.db. But perhaps at least an empty file with
the right permissions is required? Then rerun updatedb.
3. More thorough deletion of mlocate, e.g., /var/lib/mlocate still exists and
has a database.
4. Upgrade to the later version of plocate available in backports, 1.1.13-1.
But I'm not sure if the improved "upgrade from mlocate" logic will be
triggered, since the initial plocate install removed the package.
I would appreciate guidance on which, if any, of those approaches are
advisable.
COMMENTS
https://sources.debian.org/src/plocate/1.1.16-1/debian/changelog/ indicates the
1.1.8-3, had significant changes in mlocate handling, including the deletion
considered in option 3 above. 1.1.8-2 is the version in stable.
I'm guessing that the problem is related to the prior existence of mlocate and
that plocate is using mlocate's database, rather than the disk, to figure out
where to scan. Certainly my diagnostic test indicates plocate can handle btrfs
volumes.
- -- System Information:
Debian Release: 11.4
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages plocate depends on:
ii libc6 2.31-13+deb11u3
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 nocache 1.1-1+b1
ii systemd-sysv 247.3-7
-----BEGIN PGP SIGNATURE-----
iQFSBAEBCgA8FiEEreS674/HIyV9gBfdnAYPmOsbK2AFAmLXI+YeHHJvc3Nib3ls
YW5Ac3RhbmZvcmRhbHVtbmkub3JnAAoJEJwGD5jrGytgwTkH/jV8znne/5p+RgRY
TNwC5GlubDR576hCNv7Hi5/p/LaTwb4+vk0FwPAE8tt5ZkVZ+3U1aLdDt2DC5FB0
WwBjZvYyBQtpHttpery4ivAAl21t+TiD1RAOMACxXEupWZc9Wtgbbl3tvTgPY/8f
KvR/f9XJEYMwEDpKp6dwJoPa41VlWoZX8blhulIDzL2VXCZ35KlqxScRM4s/iV3x
qjNFt2XNIqSNPcd4M2K1Fttdbt8f6KMRcsC/tPAp1U1uYaCWVdouZdBiE2MTwwNU
nvk/96P2g6ndIucucmD2QDDzHgM+rBMr7OfXemlFyYbb+uYbkmLCo/mgTO406B+G
DLdPUHQ=
=8QT6
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Tue, Jul 19, 2022 at 05:46:11PM -0700, Ross Boylan wrote:
> Looking at the diagnostics below it seems that plocate has decided
> that / is a bind mount, and so updatedb skips it and everything below.
You should probably read the section on this in the updatedb.conf man page.
Long story short: btrfs sometimes uses bind mounts to implement subvolumes,
so if you want to include them, you'll need to turn off
PRUNE_BIND_MOUNTS=yes or structure your subvolume naming so that this issue
doesn't occur.
This has been discussed to death in multiple bugs already, so I'm closing
this. If you want it to be fixed, you will need to take it up with the btrfs
maintainers :-)
/* Steinar */
--
Homepage: https://www.sesse.net/
--- End Message ---
