https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #23 from Stefan Brüns <stefan.bru...@rwth-aachen.de> --- There is nothing new to add here. Please refrain from any further comments, if it does not any new information. 1. Baloo uses inodes and device ids as document IDs. inodes can be considered stable on all supported file systems, while device ids will (may) change when adding additional drives, plugging external storage in varying order, and apparently also for BTRFS subvolumes. This is a current design limitation. All this has been known for years, and also mentioned in some Phabricator tasks. Nothing new here. 2. Work has been under way to fix this for quite some time, and several places where db storage layer and filesystem layer were tightly coupled have already been cleaned up, though this is work in progress. 3. This restructuring takes time, and I only do this in my spare time. Tons of rude and abusive comments on e.g. reddit/kde and Phoronix have taken its toll, and I no longer spent the amount of time on Baloo (and KFileMetadata for the extractors) I once did. Lack of review(ers) also does not help. If you really want to support development and show some appreciation, I have a Liberapay account: https://liberapay.com/StefanB/donate -- You are receiving this mail because: You are watching all bug changes.
