Hi Cristoph, On Thu, Jun 9, 2016 at 4:55 PM, Christoph Egger <christ...@debian.org> wrote: > This is the second time sqlite managed to corrupt its database in > the last week on this system. The sqlite is located on a ext3 > filesystem with lots of free space. Unfortunately the corrupted > sqlite3 contains private keys so I can't provide the database or one > of the daily backups. May you give me pointers? Is it a big database, uses concurrent access, is the CPU load high? Any chance you may reproduce it with a non-confidental dataset? I think the best would be to subscribe to the SQLite3 users list[1]; upstream may help without giving out your data.
Regards, Laszlo/GCS [1] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
