https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #28 from tagwer...@innerjoin.org --- (In reply to postix from comment #26) > ... ntfs-3g is installed and if I see it correctly openSUSE does not offer > the newer Paragon NTFS driver ... If I remember right, the FUSE drivers don't give "stable" device numbers (that stay the same from reboot to reboot) when they mount the drive. I'm not 100% sure whether this relates to some or all FUSE drivers You would see whether this is the case or not with the "stat one-of-your-files.txt" check. Keep an eye on the Device: line (it will contain the Device numbers and Inode...) and see if you get different values each time you reboot. I think the Paragon drivers arrived in the Kernel with 5.15 so they should be there for you. > For a few files I've tried I only got a single hit with `baloosearch -i > myfile` That's good... It may be that Baloo is able to find the Filesystem ID, even through a FUSE mount and that is stable - as it is hoped to be. > > Are you watching the content indexing "as it happens" with a "balooctl > > monitor" in a separate window, again balooctl may be balooctl6 > > Nope, I am not. Might be worth looking... Normally, you would see files being listed in a batch of 40, then another batch, and another. If you get to a file "where things stop", that's suspicious... There are files that that overload Baloo, I've met scientific plots in a PDF that required massive work to unpack and sort through for the (vanishing small amount of) plain text. On the other end of the spectrum, if you have a multi gigabyte .mbox file, Baloo will try to index the contents.... -- You are receiving this mail because: You are watching all bug changes.
