Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Steinar H. Gunderson
On Mon, Nov 06, 2023 at 07:15:55PM +0100, Alain Knaff wrote: > But then, shouldn't it keep the shorter path (if both are the root of their > filesystem)? There's no heuristic that will work in all cases. What is a “shorter” path anyway; is /var/spool/tmp shorter or longer than /mnt/tmp-spool-mount

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Alain Knaff
Den 06/11/2023 19:07 huet de(n) Steinar H. Gunderson geschriwwen: On Mon, Nov 06, 2023 at 06:43:33PM +0100, Alain Knaff wrote: Nov 06 18:33:15 hitchhiker updatedb.plocate[98659]: => adding `/home' (duplicate of mount point `/run/schroot/mount/buster-53c7e4fc-0416-4408-8421-959dc1fdaa1d/home')

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Steinar H. Gunderson
On Mon, Nov 06, 2023 at 06:43:33PM +0100, Alain Knaff wrote: > Nov 06 18:33:15 hitchhiker updatedb.plocate[98659]: => adding `/home' > (duplicate of mount point > `/run/schroot/mount/buster-53c7e4fc-0416-4408-8421-959dc1fdaa1d/home') So your /home is mounted in two places, and updatedb picks on

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Alain Knaff
Den 06/11/2023 15:57 huet de(n) Steinar H. Gunderson geschriwwen: On Mon, Nov 06, 2023 at 03:41:50PM +0100, Alain Knaff wrote: On the box where plocate.db is currently corrupted, /home is a btrfs. It it by any chance a subvolume? (If so, known btrfs bug/design issue; see the updatedb.conf man

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Steinar H. Gunderson
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 th

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Steinar H. Gunderson
On Mon, Nov 06, 2023 at 03:41:50PM +0100, Alain Knaff wrote: > On the box where plocate.db is currently corrupted, /home is a btrfs. It it by any chance a subvolume? (If so, known btrfs bug/design issue; see the updatedb.conf man page.) /* Steinar */ -- Homepage: https://www.sesse.net/

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Alain Knaff
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

Bug#1055450: Plocate's database easily becomes corrupted, resulting in locate finding nothing

2023-11-06 Thread Alain Knaff
Package: plocate Version: 1.1.18-1 Hi, 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