[sqlite] backup fails despite large timeout

Hi, I'm using the following code to backup a 300MB database nightly: #!/bin/bash sqlite3 {dbfile}

Re: [sqlite] random, infrequent disk I/O errors

LITE_IOERR | (19<<8)) #define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR | (20<<8)) #define SQLITE_IOERR_SHMMAP(SQLITE_IOERR | (21<<8)) #define SQLITE_IOERR_SEEK (SQLITE_IOERR | (22<<8)) #define SQLITE_IOERR_DELETE_NOENT (SQLITE_IOERR | (23&

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

elk1...@gmail.com] Sent: Tuesday, February 26, 2013 10:32 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY On 02/27/2013 12:49 AM, Greg Janée wrote: I've instrumented the SQLite source and have found that the error is occurring at the f

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

errno=2 (ENOENT) What could not be existing? On Feb 26, 2013, at 4:01 AM, Dan Kennedy wrote: On 02/26/2013 05:22 AM, Greg Janée wrote: I'm accessing an SQLite database from two processes simultaneously. If there's contention, one process will receive an SQLITE_BUSY; that's fine. However

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

Have you set a SQLite timeout of a few seconds ? See here: I was expecting to get SQLITE_BUSY and nothing else. If the _BUSY state lasts for longer than the timeout you've set, then you'll get _IOERR. Setting a long timeout gives the

[sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

I'm accessing an SQLite database from two processes simultaneously. If there's contention, one process will receive an SQLITE_BUSY; that's fine. However, occasionally a process will receive an SQLITE_IOERR with the extended result code SQLITE_IOERR_LOCK. This seems to occur if the other