https://bugs.kde.org/show_bug.cgi?id=356357
--- Comment #8 from Riku Voipio <nc...@kos.to> --- (In reply to kdeu from comment #7) > Are there any experiences whith using LMDB and NOSYNC? Personally I've happily used that with patch attached since filing this bug - except for a handful of upgrades when I forgot the patch, only to notice that suddenly the disk light flashing means jittery UI again. Baloo makes finding files from local HD almost as easy as finding public files with google. It's really sad if people disable baloo because it's causing the desktop freeze and stutter. > Are there tools/ways to recover a corrupted database or lost transactions > with LMDB? They might not even exist yet, if people don't use NOSYNC. You are assuming that under current configuration LMDB can't get corrupted. File systems are nasty and even with fdatasync there are caveats. But for most users, sudden crashes (especially in middle of transactions) is really rare events. Lost transactions are not a problem, entries would be just regenerated in next index scanning. Recovering the DB is somewhat pointless - you can just regenerate it from scratch, if under idle iopriority the indexing really has no user impact. -- You are receiving this mail because: You are watching all bug changes.
