https://bugs.kde.org/show_bug.cgi?id=435294
--- Comment #6 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #2) > Journalctl(*) shows a matching... > > Apr 01 12:21:38 localhost.localdomain baloo_file[1100]: 5714849124383745 > "/home/test/Documents/temp/file1.txt" renaming "kdeglobals" to "file1.txt" > Apr 01 12:21:38 localhost.localdomain baloo_file[1100]: 5643818955242497 > "/home/test/.kde/share/config/kdeglobals" renaming "Trolltech.conf" to > "kdeglobals" > > I'm guessing these "renamings" are not real. If I look back through the logs > there are some large batches of these messages. If this is thread creep, apologies... I want to flag the issue here but maybe should follow it on Bug 435434 Having had a look through batches of "renaming" failures/messages, the files mentioned are newly created. I suspect deleted and rewritten, with newly created files reusing "just released" inodes. Is baloo proof against this? Gut feeling is it makes life that *little* bit more difficult. I am assuming if you delete a file and create a directory, you don't get the same inode. Could be though that that assumption is not correct in all cases :-/ I'm looking on Neon Testing (and an ext4 filesystem). I don't see any "renaming" messages on Fedora (BTRFS) ... Information from https://stackoverflow.com/questions/51019714/does-recreating-a-file-reuse-the-previous-inode -- You are receiving this mail because: You are watching all bug changes.
