https://bugs.kde.org/show_bug.cgi?id=438434
--- Comment #10 from Martin Steigerwald <mar...@lichtvoll.de> ---
% baloosearch --id testfile.txt | grep testfile.txt | head -2
Verstrichen: 14,6812 msec
23479b00000020 /home/martin/testfile.txt
23479b00000021 /home/martin/testfile.txt
% LANG=en balooshow -x 23479b00000020
23479b00000020 32 2312091 /home/martin/testfile.txt
Mtime: 1623421630 2021-06-11T16:27:10
Ctime: 1623421630 2021-06-11T16:27:10
Internal Info
Terms: Mplain Mtext T5 T8
File Name Terms: Ftestfile Ftxt
XAttr Terms:
% LANG=en balooshow -x 23479b00000021
23479b00000021 33 2312091 /home/martin/testfile.txt
Mtime: 1623421630 2021-06-11T16:27:10
Ctime: 1623421630 2021-06-11T16:27:10
Cached properties:
Line Count: 1
Internal Info
Terms: Mplain Mtext T5 T8 X20-1 hello penguin
File Name Terms: Ftestfile Ftxt
XAttr Terms:
lineCount: 1
Does that mean that Baloo saw two different device numbers (32 and 33)?
There have been several reboots and it may be that at a certain point the
device number has been different, I just checked for the device number as I
actually noticed Baloo was re-indexing files. So maybe the re-indexing was
triggered by a different device number from a boot in between?
I still think relying on the device number creates more problems than it
solves. I hope you understand that I am not willing to change my setup dm-crypt
with LUKS, LVM and then BTRFS (single) on top of it, to be able to guarantee a
stable device number. I do think the device number is not supposed to be of
relevance for any application and is not guaranteed to be stable in Linux, but
I can certainly ask Linux kernel developers about their take on this.
But maybe I misread the above output. Anyway, I hope it helps.
--
You are receiving this mail because:
You are watching all bug changes.
