On Mon, Jan 11, 2010 at 10:09 AM, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > I wrote: >> I have recently had an apparently isolated failure of a program making >> some updates to a sqlite database. The only information I have is >> this error message: >> >> DBD::SQLite::st execute failed: disk I/O error(10) at dbdimp.c line 423 >> [for Statement "SELECT * FROM sell NATURAL LEFT JOIN commods WHERE >> commodname IS NULL"] at CommodsDatabase.pm line 158. >> PROCESSING FAILED >
Try running the above statement from the sqlite shell. If you still get the error, something is fubar with your db. If not, something is fubar with your Perl implementation. Not much help, but this might take you a step or two further. > This has just happened again, twice, recently. What additional > instrumentation should I apply to my system to find out the cause ? > > I'm using the Debian package sqlite3 3.5.9-6 on Debian lenny i386, > in Perl, via DBD::SQLite (libdbd-sqlite3-perl 1.14-3). > > As I wrote earlier: > > CommodsDatabase.pm is my code. That part is doing a consistency check > before saying COMMIT. I don't know exactly what sqlite was doing, but > I was alarmed. I checked my system logs and there are no reports of > problems with the disks. There are no reports of the filesystem > having been full and while possible it doesn't seem likely. > > Ian. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
