https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #35 from tagwer...@innerjoin.org --- (In reply to Joachim Wagner from comment #34) > ... Hence my proposal > to move away from system-provided IDs and to use the mount point > as an identifier instead ... Accepted. Although I think we need to look at "what we can trust most". If ext2/3/4, BTRFS, NTFS give a stable filesystem ID, we should make the most of it to help when mounting storage on a different mount point (saying, yes, we know this disc) or when mounting different storage on a fixed mount point (this isn't the disc it used to be). If the mount point and Filesystem ID disagree, provided it's a reliable Filesystem ID, we should go with that Filesystem ID This would mean including the filesystem ID in your "I" table and careful making judgements when a disc is seen to move, vanish or reappear. Having kept tabs on baloo issues for a couple of years, the majority of the "reindexing" or "duplicated results" issues have been from OpenSUSE and thus BTRFS with multiple subvols. I don't remember seeing any reports mentioning XFS but then you are not prompted for filesystem type when submitting a bug report. Maybe there were some that mentioned Mandriva but I never got to the bottom of those. I don't know the status with ZFS. If we wanted an intellectual challenge to shake out the edge cases, we can think how to deal with symbolic links 8-] -- You are receiving this mail because: You are watching all bug changes.
