Nikolaus Rath writes ("Re: [sqlite] Unexplained "disk i/o error", Unix"):
> You can try to run the program under strace and check for failed system
> calls.
This is in principle possible but given that the problem is
intermittent it might just make it go away. Also strace has some
process- and signal-handling bugs which can perturb things.
I'll do this if there's no better way. Really I would like sqlite to
report the errno value! It's tempting to recompile it with a bunch of
fprintf(stderr...);
P Kishor writes ("Re: [sqlite] Unexplained "disk i/o error", Unix"):
> On Mon, Jan 11, 2010 at 10:09 AM, Ian Jackson
> <ijack...@chiark.greenend.org.uk> wrote:
> > I wrote:
> >> 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.
You've apparently missed me saying that the problem is intermittent.
This statement works fine from the sqlite shell every time I've tried
it by hand, but it also works fine 90-99% of the time the Perl script
runs it.
Ian.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
