Re: [sqlite] Cause of "disk I/O errors"

2011-02-01 Thread Nasron Cheong
I did report an issue much earlier on with regards to retrying io operations when some other process (like virus scanners) are touching the db file. Hopefully it will be of use to you: http://www.mail-archive.com/sqlite-users@sqlite.org/msg51895.html - Nasron Cheong

Re: [sqlite] Cause of "disk I/O errors"

2011-01-31 Thread Teg
Hello GHCS, Most common problem my users have is Virus scanners stepping on my writes. Might suggest they tell their Virus scanners to ignore your data folder. People do run out of disk space fairly frequently. I wouldn't discount it out of hand. C Sunday, January 30, 2011, 8:25:48 PM, you

Re: [sqlite] Cause of "disk I/O errors"

2011-01-30 Thread Max Vlasov
On Mon, Jan 31, 2011 at 4:25 AM, GHCS Software wrote: > > So it seems it must be something about their particular machine > environment, but what? I'm sure that nobody is running out of disk space > these days. Any ideas on where to look or what to suggest to them that >

Re: [sqlite] Cause of "disk I/O errors"

2011-01-30 Thread Jay A. Kreibich
On Sun, Jan 30, 2011 at 08:25:48PM -0500, GHCS Software scratched on the wall: > Are there any common reasons for encountering a "disk I/O error" (code > 10) when creating records in an SQLite database on a Windows PC? Check to be sure the application has permission to create new files in

Re: [sqlite] Cause of "disk I/O errors"

2011-01-30 Thread Simon Slavin
On 31 Jan 2011, at 1:25am, GHCS Software wrote: > Are there any common reasons for encountering a "disk I/O error" (code > 10) when creating records in an SQLite database on a Windows PC? [snip] > > So it seems it must be something about their particular machine > environment, but what? File

[sqlite] Cause of "disk I/O errors"

2011-01-30 Thread GHCS Software
Are there any common reasons for encountering a "disk I/O error" (code 10) when creating records in an SQLite database on a Windows PC? My product uses V3.6.23.1 and I did not have extended error codes turned on in my releases up to now. The problem in reproducing this is that the users can be