https://bugs.kde.org/show_bug.cgi?id=450171
--- Comment #19 from tagwer...@innerjoin.org --- (In reply to linuxfluesterer from comment #18) > ... the 'dummy' file appeared finally three times in 'baloosearch Alle_Tags' > ... The problem is Baloo is on shifting sands, it "sees" files reappear with different ID's and thinks they are new files. > ... this interesting link, which confirms the problem with the Device ID: > https://www.reddit.com/r/kde/comments/dhd14c/baloo_cant_index_nfs_mount/ Baloo is critically dependent on file-locking, there's the indexing process writing information to the file and other processes wanting to read the index in order to do searches. Locking has *got* to work. There's also a lot of information that has to be written quickly to the index during the indexing (particularly content indexing); the .local/share/baloo folder has to be on a local disc; better if the local disc is an SSD. Maybe it's possible to index remote filesystems. Although, as you see, there's a labyrinth of different traps and pitfalls to navigate. With your sshfs mount, did you watch to see whether the file ID's (device number/inode) stayed "fixed" or did they also change? There's a missing piece of the puzzle; it should be that whatever NAS you are using can index the files itself/locally and what the client does is ask the server for the search results. I've no idea whether anyone is doing that, it would be a big project... Sorry! -- You are receiving this mail because: You are watching all bug changes.
