Hi All, We have been upgrading our embedded Linux system to version 3.7.7.1 of SQLite. We had hopes of using WAL mode to cure some of the database locking issues that we have had. Not sure if it matters but we are running an ARM9 with JFFS2 file system. We are using a very old kernel 2.6.8.1, I'm not sure that has anything to do with it or not. The following test on the embedded platform illustrates what we are seeing. test.db doesn't exist prior to running this test. ~ # sqlite3 test.db SQLite version 3.7.7.1 2011-06-28 17:39:05 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table test (test integer); sqlite> .tables test sqlite> .exit ~ # sqlite3 test.db SQLite version 3.7.7.1 2011-06-28 17:39:05 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .tables test sqlite> pragma journal_mode=wal; wal sqlite> .tables Error: disk I/O error sqlite>
When a database is in journal_mode=wal, it always returns disk I/O error. When I look at the files, there are three files for this database. test.db, test.db-shm, and test.db-wal. Any ideas on what may be causing this error and any suggestions for a work-around? Korey _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
