https://bugs.kde.org/show_bug.cgi?id=438434
--- Comment #2 from Martin Steigerwald <mar...@lichtvoll.de> --- I used a BTRFS RAID 1 before, but this time it is not. "Baloo expects the device number / inode for files to be stable (not change every reboot)" If it changes though, for whatever reason, even though I use a single BTRFS filesystem on the very same LUKS encrypted partition and on LVM, then the requirement that the device number is stable, is broken. Remember, we are talking about $HOME. I'd say that in 99% of all desktop use cases, $HOME is not a wildly different filesystem on every reboot. So please, pretty please *stop* relying on an internal operating system detail (device number) to be stable for it. It is all about usability here. Telling regular users to check whether their device numbers are stable *just* to make indexing work reliable is not going to fly regarding usability. I imagine asking my father checking for a device number… seriously… please stop… relying on OS internals like an inode number or even a device number to be stable. This assumption is terminally broken, as has been shown here repeatedly. Do you know any user of KDE Plasma who expects Baloo to reindex their unchanged files in $HOME, just cause they may have a different $HOME on every reboot? If Baloo relies on this, this is at the last a bad design choice. I'd go further than that and I'd say its terminally broken regarding usability. Imagine if I find out that the device number would change… what would I do? Reinstall the system to match the assumptions of Baloo? Not going to happen. Do whatever you need to do about removeable media, but just, assume, pretty please assume, that $HOME will be the same directory tree on the same laptop for years to come. And even if I copy it to another laptop… why would Baloo even care? It is still the very same directory tree. Nothing, I repeat, nothing of interest for Baloo has changed. Baloo has no business whatsoever to use the device number for anything related to indexing. Pretty please consider this input instead of dismissing it. The functionality is broken cause it relies on a broken assumption. Please fix it. Thank you dearly for your consideration. -- You are receiving this mail because: You are watching all bug changes.
