https://bugs.kde.org/show_bug.cgi?id=435294
--- Comment #13 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #12)
> What I don't know is whether this is bad(tm)
Oooooo...
There could be a problem in that device numbers are not necessarily fixed.
Looking at openSuse that has a set of BTRFS subvols. /Home is a subvol and its
minor device number can (and does) change on reboot.
You can see this by creating a testfile, "stat" it to get the device number,
check that that device number appears in the balooshow results. Then reboot and
stat the file again.
I get, for example:
$ stat testfile.txt
File: testfile.txt
Size: 14 Blocks: 8 IO Block: 4096 regular file
Device: 38h/56d Inode: 5089 Links: 1
...
followed by, after a reboot:
$ stat testfile.txt
File: testfile.txt
Size: 14 Blocks: 8 IO Block: 4096 regular file
Device: 35h/53d Inode: 5089 Links: 1
...
I think baloo sees the change and reindexes the files...
I've asked on Bug 402154 "Baloo reindexes everything after every reboot" to do
this test and see if they see the device number changing....
It maybe that there's also a connection to Bug 401863
--
You are receiving this mail because:
You are watching all bug changes.
