On 12/21/17, Nikhil Deshpande <ndeshpa...@vmware.com> wrote: > > There were no power-off or reboots in near time vicinity when the > corruption was detected.
(1) Might the corruption have been sitting dormant due to some far away power-off or reboot and was only recently discovered? How much do you trust the fsync() system call and the filesystems ability to honor that system call on the VM on which this code is running? Do you run "PRAGMA quick_check" on initial power-up? (2) Is this the only corruption instance you have seen? (3) The showdb outputs you sent only shows me the first 8 bytes of the page. From those 8 bytes, it looks to be an overflow page that is being used as a btree page. Are there any further clues in the hex dump of the bad pages? (4) What does "showdb pgidx" look like? (5) How many threads are accessing the database? Are you sure that you have the database set in a thread-safe mode? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
