Comment 13 for bug 346912

QDBM failure is likely to be a result of not using fsync in conjunction with one of the following

1) use of Ext4. Not a problem on ext3 as an sqlite fsync would automatically fsync QDBM
2) Use of suspend/resume while tracker is indexing. This has caused tracker to corrupt QDBM index in the past. Not sure why this is so but does not affect sqlite

I agree that sqlite FTS should solve above two cases as Ive seen no reports of the sqlite db getting corrupted