Re: [sqlite] How to Troubleshoot Disk I/O Error
URGE pid=2776, deleteFlag=0 CLOSE file=34 UNMAP-FILE pid=2776, pFile=3E0398, hMap=0, pMapRegion=0, mmapSize=0, mmapSizeActual=0, mmapSizeMax=0 UNMAP-FILE pid=2776, pFile=3E0398, rc=SQLITE_OK CLOSE file=0, rc=ok CLOSE file=30 UNMAP-FILE pid=2776, pFile=215BD8, hMap=0, pMapRegion=0, mmapSize=0, mmapSizeActual=0, mmapSizeMax=0 UNMAP-FILE pid=2776, pFile=215BD8, rc=SQLITE_OK CLOSE file=0, rc=ok UNLOCK file=2C, oldLock=4(0), newLock=0 READ-UNLOCK file=2C, lock=4 READ-UNLOCK file=2C, rc=SQLITE_OK UNLOCK file=2C, lock=0, rc=SQLITE_OK CLOSE file=2C UNMAP-FILE pid=2776, pFile=214C18, hMap=0, pMapRegion=0, mmapSize=0, mmapSizeActual=0, mmapSizeMax=0 UNMAP-FILE pid=2776, pFile=214C18, rc=SQLITE_OK CLOSE file=0, rc=ok OPEN name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db, pFile=214480, flags=106, pOutFlags=12F09C OPEN file=30, name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db, access=c000, rc=ok OPEN file=30, name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db, access=c000, pOutFlags=12F09C, *pOutFlags=2, rc=ok FCNTL file=30, op=18, pArg=12EE94 FCNTL file=30, rc=SQLITE_OK FCNTL file=30, op=18, pArg=12F078 FCNTL file=30, rc=SQLITE_OK READ file=30, buffer=12F2C8, amount=100, offset=0, lock=0 READ file=30, rc=SQLITE_IOERR_SHORT_READ FCNTL file=30, op=15, pArg=214420 FCNTL file=30, rc=SQLITE_NOTFOUND FCNTL file=30, op=18, pArg=12F044 FCNTL file=30, rc=SQLITE_OK FCNTL file=30, op=14, pArg=12EB64 FCNTL file=30, rc=SQLITE_NOTFOUND LOCK file=30, oldLock=0(0), newLock=1 READ-LOCK file=30, lock=0 READ-LOCK file=30, rc=SQLITE_ERROR LOCK file=30, lock=1, rc=SQLITE_OK ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-journal, flags=0, pResOut=12DDA8 ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-journal, pResOut=12DDA8, *pResOut=0, rc=SQLITE_OK SIZE file=30, pSize=12DCB4 SIZE file=30, pSize=12DCB4, *pSize=0, rc=SQLITE_OK DELETE name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal, syncDir=0 DELETE name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal, rc=SQLITE_IOERR_DELETE_NOENT SIZE file=30, pSize=12DDB0 SIZE file=30, pSize=12DDB0, *pSize=0, rc=SQLITE_OK UNLOCK file=30, oldLock=1(0), newLock=0 READ-UNLOCK file=30, lock=1 READ-UNLOCK file=30, rc=SQLITE_ERROR UNLOCK file=30, lock=0, rc=SQLITE_OK LOCK file=30, oldLock=0(0), newLock=1 READ-LOCK file=30, lock=0 READ-LOCK file=30, rc=SQLITE_ERROR LOCK file=30, lock=1, rc=SQLITE_OK ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-journal, flags=0, pResOut=12DCA0 ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-journal, pResOut=12DCA0, *pResOut=0, rc=SQLITE_OK SIZE file=30, pSize=12DCA8 SIZE file=30, pSize=12DCA8, *pSize=0, rc=SQLITE_OK SIZE file=30, pSize=12DBAC SIZE file=30, pSize=12DBAC, *pSize=0, rc=SQLITE_OK DELETE name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal, syncDir=0 DELETE name=D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal, rc=SQLITE_IOERR_DELETE_NOENT SIZE file=30, pSize=12DCA8 SIZE file=30, pSize=12DCA8, *pSize=0, rc=SQLITE_OK UNLOCK file=30, oldLock=1(0), newLock=0 READ-UNLOCK file=30, lock=1 READ-UNLOCK file=30, rc=SQLITE_ERROR UNLOCK file=30, lock=0, rc=SQLITE_OK UNLOCK file=30, oldLock=0(0), newLock=0 UNLOCK file=30, lock=0, rc=SQLITE_OK CLOSE file=30 UNMAP-FILE pid=2776, pFile=214480, hMap=0, pMapRegion=0, mmapSize=0, mmapSizeActual=0, mmapSizeMax=0 UNMAP-FILE pid=2776, pFile=214480, rc=SQLITE_OK CLOSE file=0, rc=ok - Original Message - From: sqlite-users@sqlite.org To: sqlite-users@sqlite.org At: Feb 20 2014 09:49:37 On 02/20/2014 09:29 PM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) wrote: > Our client got the following print-out. First hint of failure is the line > "TRUNCATE 48 32768 failed". Any insights into what the root cause might be ? The operation that is failing is (probaby) an attempt to use SetEndOfFile() to extend the size of the *-shm file to 32KB (from 0KB). I have no idea why it is failing. What version of SQLite is this? Newer versions provide more detail for debugging, particularly if you also turn on sqlite3_log() logging: http://sqlite.org/c3ref/log.html Dan. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] How to Troubleshoot Disk I/O Error
Our client got the following print-out. First hint of failure is the line "TRUNCATE 48 32768 failed". Any insights into what the root cause might be ? OPEN 40 D:\blp\wintrv\smartclient\applications\appinfo.db 0xc000 ok READ 40 lock=0 LOCK 40 1 was 0(0) READ 40 lock=1 OPEN 44 D:\blp\wintrv\smartclient\applications\appinfo.db-wal 0xc000 ok OPEN 48 D:\blp\wintrv\smartclient\applications\appinfo.db-shm 0xc000 ok SHM-LOCK 48 ok LockFileEx 0x TRUNCATE 48 0 TRUNCATE 48 0 ok SHM-LOCK 48 ok UnlockFileEx 0x SHM-LOCK 48 ok LockFileEx 0x SHM-LOCK 48 ok LockFileEx 0x SHM-LOCK shmid-0, pid-7308 got 000,001 ok TRUNCATE 48 32768 TRUNCATE 48 32768 failed SHM-LOCK 48 ok UnlockFileEx 0x SHM-LOCK shmid-0, pid-7308 got 000,000 ok Error occurred-> SQLITE_IOERR[10]: disk I/O error LOCK 40 4 was 1(0) unreadlock = 1 TRUNCATE 48 32768 TRUNCATE 48 32768 failed CLOSE 48 CLOSE 48 ok CLOSE 44 CLOSE 44 ok UNLOCK 40 to 0 was 4(0) CLOSE 40 CLOSE 40 ok OPEN 44 D:\blp\wintrv\smartclient\applications\appinfo.backup.db 0xc000 ok READ 44 lock=0 LOCK 44 1 was 0(0) DELETE "D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal" failed UNLOCK 44 to 0 was 1(0) LOCK 44 1 was 0(0) DELETE "D:\blp\wintrv\smartclient\applications\appinfo.backup.db-wal" failed UNLOCK 44 to 0 was 1(0) UNLOCK 44 to 0 was 0(0) CLOSE 44 CLOSE 44 ok Thanks, Akintoye ----- Original Message - From: Akintoye Olorode (BLOOMBERG/ 731 LEXIN) To: sqlite-users@sqlite.org At: Jan 30 2014 10:52:17 Thanks, will try this suggestions and post results. - Akintoye - Original Message - From: sqlite-users@sqlite.org To: sqlite-users@sqlite.org At: Jan 30 2014 10:44:45 On 01/30/2014 10:19 PM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) wrote: > Hi, > > We have one client that recently upgraded from WinXP SP3 to Win7 sp1 > (Japanese Language). With new OS, attempts to access read from our sqlite > database fails with disk I/O error. > > Can anyone help with suggestions on how to troubleshoot disk I/O error ? > Adding call to sqlite3_config(SQLITE_CONFIG_LOG, ...) produces no additional > information. > > We have not been able to reproduce the error in-house.The user has HP ENVY > laptop with hybrid drive. User has tried : > > 1. Install latest file system drivers > 2. reformat the hard-drive & reinstall Win7 OS > > > all to no avail. Client does not report problems with any other applications. Immediately after the error occurs, what value is returned by the sqlite3_extended_errcode() function? Often the extended error code identifies the specific IO operation that failed, which can shed light on the problem. Another thing to do is to try compiling with the following defines: -DSQLITE_DEBUG=1 -DSQLITE_DEBUG_OS_TRACE=1 This causes the Windows VFS module to print various messages to standard output that should help to figure out what is happening. Dan. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] How to Troubleshoot Disk I/O Error
Error is-> SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */ - Akintoye - Original Message - From: pontia...@gmail.com To: Akintoye Olorode (BLOOMBERG/ 731 LEXIN), sqlite-users@sqlite.org At: Jan 30 2014 10:38:53 What exact Disk I/O error are you getting? There are many different types. - Permissions to read are denied - Invalid characters in the filename - Corrupted database etc On Thu, Jan 30, 2014 at 10:19 AM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) wrote: Hi, We have one client that recently upgraded from WinXP SP3 to Win7 sp1 (Japanese Language). With new OS, attempts to access read from our sqlite database fails with disk I/O error. Can anyone help with suggestions on how to troubleshoot disk I/O error ? Adding call to sqlite3_config(SQLITE_CONFIG_LOG, ...) produces no additional information. We have not been able to reproduce the error in-house.The user has HP ENVY laptop with hybrid drive. User has tried : 1. Install latest file system drivers 2. reformat the hard-drive & reinstall Win7 OS all to no avail. Client does not report problems with any other applications. Thank You, Akintoye ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] How to Troubleshoot Disk I/O Error
Thanks, will try this suggestions and post results. - Akintoye - Original Message - From: sqlite-users@sqlite.org To: sqlite-users@sqlite.org At: Jan 30 2014 10:44:45 On 01/30/2014 10:19 PM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) wrote: > Hi, > > We have one client that recently upgraded from WinXP SP3 to Win7 sp1 > (Japanese Language). With new OS, attempts to access read from our sqlite > database fails with disk I/O error. > > Can anyone help with suggestions on how to troubleshoot disk I/O error ? > Adding call to sqlite3_config(SQLITE_CONFIG_LOG, ...) produces no additional > information. > > We have not been able to reproduce the error in-house.The user has HP ENVY > laptop with hybrid drive. User has tried : > > 1. Install latest file system drivers > 2. reformat the hard-drive & reinstall Win7 OS > > > all to no avail. Client does not report problems with any other applications. Immediately after the error occurs, what value is returned by the sqlite3_extended_errcode() function? Often the extended error code identifies the specific IO operation that failed, which can shed light on the problem. Another thing to do is to try compiling with the following defines: -DSQLITE_DEBUG=1 -DSQLITE_DEBUG_OS_TRACE=1 This causes the Windows VFS module to print various messages to standard output that should help to figure out what is happening. Dan. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] How to Troubleshoot Disk I/O Error
Hi, We have one client that recently upgraded from WinXP SP3 to Win7 sp1 (Japanese Language). With new OS, attempts to access read from our sqlite database fails with disk I/O error. Can anyone help with suggestions on how to troubleshoot disk I/O error ? Adding call to sqlite3_config(SQLITE_CONFIG_LOG, ...) produces no additional information. We have not been able to reproduce the error in-house.The user has HP ENVY laptop with hybrid drive. User has tried : 1. Install latest file system drivers 2. reformat the hard-drive & reinstall Win7 OS all to no avail. Client does not report problems with any other applications. Thank You, Akintoye ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
