Hi, Thank you for the suggestion. The sqlite3_extended_errcode() is 1034 disk I/O error. Regards Arun
---- On Fri, 12 Apr 2019 17:06:00 +0530 Richard Hipp <d...@sqlite.org> wrote ---- > On 4/12/19, Arun - Siara Logics (cc) <a...@siara.cc> wrote: > > fn:DirectWrite:Success > > fn:FlushBuffer:Success > > fn:Sync:Success > > SQL error: disk I/O error > > > > At the end, there are two files on disk: vfs_test.db (0 bytes) and > > vfs_test.db-journal (512 bytes). There is no problem reading a database. > > But when CREATE or INSERT is involved, it gives disk I/O error. > > > > Any idea why it is throwing disk I/O error, inspite of the previous sync > > success? Any suggestions on how I could figure it out? > > Please tell us the sqlite3_extended_errcode(). Also, consider > enabling the error and warning log > (https://www.sqlite.org/errlog.html) > > > > > > Regards > > Arun > > > > > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
