Den 06/11/2023 15:31 huet de(n) Steinar H. Gunderson geschriwwen:
On Mon, Nov 06, 2023 at 03:09:48PM +0100, Alain Knaff wrote:
On 2 separate Debian 12 machines, I'm observing the following issue:
Search for a file that obviously exists returns nothing.
Running updatedb and then locate doesn't fix this.
Removing /var/lib/plocate/plocate.db, and then re-running updatedb does fix
it... until the issue reappears again several days later.
I haven't had reports that this is a common occurrence, no. There were some
issues with upgrades from mlocate, but nothing obvious.
That's what I suspected at first as well. But then I uninstalled mlocate
complete (dpkg --purge mlocate , and removed files containing mlocating
that were still left after the purge), but the problem kept re-occuring.
You could in theory
dump out what's in plocate.db and see what it looks like? (E.g. through
plocate '' as root.)
On one of the 2 boxes (where I didn't recently perform above-mentioned
workaround), I see that plocate.db is not empty, but everything under
/home seems to be missing (i.e. /home itself is present, but everything
contained in it is missing)
What filesystem is this?
On the box where plocate.db is currently corrupted, /home is a btrfs.
On the other box, where I just applied the workaround, /home is an ext FS
Could there be something very wrong with timestamps?
What exactly would that be, and how to check for it?
/* Steinar */
Thanks for your quick answer,
Alain
