If it helps the discussion any, we are using JFFS file system on Linux 2.6.8.1.
We are running uclibc, not sure if that matters or not. And one more thing, we updated from an old version of SQLite that has been in our product (and stable) for years. (I want to say it was 3.3.something.) We didn't have any problems until updating to the latest version and enabling WAL mode. I hope that this helps, Thanks, Korey -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Stephan Beal Sent: November 1, 2011 7:46 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Disk I/O Error On Mon, Oct 31, 2011 at 10:44 PM, Richard Hipp <d...@sqlite.org> wrote: > If an interrupt occurs that stops the read before it can complete, > then the read should be tried again. > http://www.sqlite.org/src/artifact/07acbb3e074e?ln=2968 This topic came up before a few months ago and someone (don't remember who) pointed out that platforms exist which can return >0 from read() when interrupted. My man page says: POSIX allows a read() that is interrupted after reading some data to return -1 (with errno set to EINTR) or to return the number of bytes already read. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
