https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #51 from tagwer...@innerjoin.org --- (In reply to Nate Graham from comment #49) > Nice, please do submit it as a merge request! Does sound good, not least because it's starting to affect Fedora BTRFS systems. Used to be nearly always OpenSUSE that had trouble. Is there a list anywhere of "what the FSID is"? We will definitely meet NTFS (both as the Fuse NTFS-3G and the Paragon code), we will meet encrypted volumes and remote filesystems (Samba and NFS), ExFat as well. We might meet ZFS and also possibly(?) OverlayFS. Baloo is not supported for all of these but it doesn't stop people trying :-) I agree, it would be prudent to "clean and start afresh", at least if people are content indexing. It might also clear out existing corruptions (Bug 464226). Heads up though that there's been a recent change to severely limit the amount of memory baloo can use: https://invent.kde.org/frameworks/baloo/-/commit/db223ed1fe300c0809b743711eda55364a67a491 that could impact reindex (currently it's initial "what files are where" scan is a single transaction: Bug 394750 and wander down to the 13th comment) A note that Igor Pobioko has been doing stuff and that https://invent.kde.org/poboiko/baloo/-/commit/b17e96700f3da2202e27bf80fe423c458c3cc62d might be useful. Wishing you good luck! ~ -- You are receiving this mail because: You are watching all bug changes.
