On Sat, May 30, 2009 at 7:43 AM, John Machin <[email protected]> wrote: > On 17/04/2009 1:39 AM, Filip Navara wrote: >> Hello, >> >> I have expected at least some reply. Oh well, new the corruption has happened >> again (on another different machine) and I have saved the database files. One >> of the corrupted files is available at >> http://www.emclient.com/temp/folders.zip. > > Ummmm ... your first message [scroll down to read] is talking about > *incremental* vacuuming; however the database file that you made > available has FULL (not incremental) auto-vacumming set.
I switch to incremental vacuum mode at run-time once the database is opened. > Six orphan pages at the end of the file plus another 3 orphans suggests > that an auto-vacuum (full or incremental) may have been interrupted -- > or perhaps later given that you are? were? using synchronous=off. While I was using synchronous=off in this instance, it happened even with synchronous=FULL. There was never a power failure during the tests, only the application may have been killed few times. > Did you get any resolution on this? Updating to latest SQLite, which includes change #6413, fixed it. Unfortunately it created a lot of other problems that are hopefully now solved with the 3.6.14.2 release. Best regards, Filip Navara _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
