Could someone please clarify the ext4 issue? - Does tracker 0.6.9x generally have to get corrupted DBs due to a QDBM-ext4-issue? - Is there a different solution other than reformatting to ext3 or xyz-fs or waiting for tracker 0.7.x? - Specifically: Would it be viable to come up with some special QDBM-build for ext4-users - or would something like that be too slow due to heavy syncing? - Finally: Could tracker find out (at install/configuration time) if its DBs are sitting in an ext4-minefield and throw up a warning dialogue or something?
-- Tracker index corruption (was Tracker does not stop indexing) https://bugs.launchpad.net/bugs/346912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
