https://bugs.kde.org/show_bug.cgi?id=488446
--- Comment #23 from [email protected] --- (In reply to contact from comment #22) > Okay, the index is now done building. I think with 1GB it is still quite > considerable for a 300GB drive, but as far as I can tell it did not > double-index any files and also reached 100%. Ohh! That was pretty quick, given what you were dealing with before... The double indexing is "historical" and the result of the way BTRFS worked. The issue used to catch OpenSUSE specially and more recently Fedora. BTRFS on an encrypted partition may be an extra complexity. I will add Nixos to my mental list though I think if you are content indexing with a load of files, you said 500,000?, a 1GB index is quite fair. > Feel free to close this bug if you think all issues have been resolved. The > one that we were able to pinpoint has been moved into it's own thing. I think we can close this one and Bug 488446 but leave Bug 488533 open so we can follow the issue with "model/obj" > I will also create an enhancement discussion on duscuss.kde.org around this. Thank you for your efforts and engagement in tracking this down. -- You are receiving this mail because: You are watching all bug changes.
