Hi!

"László Böszörményi (GCS)" <g...@debian.org> writes:
> 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,

~1.3 MiB

> uses concurrent access,

There's two processes accessing the database. It also currently runns in
WAL mode.

> is the CPU load high?

CPU can get max'ed. This is just a 900MHz mipsel and it's some things
that require quite some computation

> Any chance you may reproduce it with a non-confidental dataset?

I can try. Not in the next 2 weeks though, sorry.

  Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

Reply via email to