subject:"Re\: \[sqlite\] How to Troubleshoot Disk I\/O Error"

Re: [sqlite] How to Troubleshoot Disk I/O Error

2014-02-26 Thread RSmith



On 2014/02/26 16:27, Richard Hipp wrote:

LOG: os_win.c:33842: (33)
winTruncate2(D:\blp\wintrv\smartclient\applications\appinfo.db-shm) -
ãƒ—ãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã  ã ¾ã ›ã‚“ã€‚åˆ¥ã
®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã,
extended-result-code: 1546
TRUNCATE file=34, rc=SQLITE_IOERR_TRUNCATE
LOG: os_win.c:35002: (33)
winShmMap2(D:\blp\wintrv\smartclient\applications\appinfo.db) -
ãƒ—ãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã  ã ¾ã ›ã‚“ã€‚åˆ¥ã
®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã ¦ã  E,
extended-result-code: 4874


What happened here is that SQLite tried to invoke SetEndOfFile() on a
shared-memory file in order to change its size from 0 bytes to 32768
bytes.  But it got back an SQLITE_LOCK_VIOLATION error (windows error code
33).

I'm not sure why this is happening. The file had just been created - could
it be that some anti-virus software had the file locked down in order to
scan it somehow?

The unreadable text is the error message that Windows provided via
FormatMessageW().  Clearly it is not in English.  Do you know what the
locale setting is for the machine that is generating this error?


Also possible: File is in a folder that is synced using Windows Briefcase (on older computers typically) or a Dropbox/OneDrive 
folder or such.
Or in a UAC protected place (the create could work fine but the change request may be killed, although the create should set the 
owner correctly which shouldn't really have change request issues then, unless some setting doesn't see this happen correctly).


But from all the above, I think Antivirus or other real-time computer 
protection or some such is most likely.

___
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

2014-02-26 Thread Richard Hipp

On Wed, Feb 26, 2014 at 9:04 AM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) <
aolor...@bloomberg.net> wrote:

> I recompiled with v 3.8.3.1 and enabled sqlite3_log (lines starting with
> "LOG:"  in output). Result below. Thanks.
>
>
Thanks for the enhanced log.  Very helpful!



> LOG: os_win.c:33842: (33)
> winTruncate2(D:\blp\wintrv\smartclient\applications\appinfo.db-shm) -
> ãƒ—ãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã  ã ¾ã ›ã‚“ã€‚åˆ¥ã
> ®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã,
> extended-result-code: 1546
> TRUNCATE file=34, rc=SQLITE_IOERR_TRUNCATE
> LOG: os_win.c:35002: (33)
> winShmMap2(D:\blp\wintrv\smartclient\applications\appinfo.db) -
> ãƒ—ãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã  ã ¾ã ›ã‚“ã€‚åˆ¥ã
> ®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã ¦ã  E,
> extended-result-code: 4874
>

What happened here is that SQLite tried to invoke SetEndOfFile() on a
shared-memory file in order to change its size from 0 bytes to 32768
bytes.  But it got back an SQLITE_LOCK_VIOLATION error (windows error code
33).

I'm not sure why this is happening. The file had just been created - could
it be that some anti-virus software had the file locked down in order to
scan it somehow?

The unreadable text is the error message that Windows provided via
FormatMessageW().  Clearly it is not in English.  Do you know what the
locale setting is for the machine that is generating this error?
-- 
D. Richard Hipp
d...@sqlite.org
___
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

2014-02-26 Thread Akintoye Olorode (BLOOMBERG/ 731 LEXIN)

I recompiled with v 3.8.3.1 and enabled sqlite3_log (lines starting with "LOG:" 
 in output). Result below. Thanks.

validate smartclient appinfo database
OPEN name=D:\blp\wintrv\smartclient\applications\appinfo.db, pFile=214C18, 
flags=106, pOutFlags=12F09C
OPEN file=2C, name=D:\blp\wintrv\smartclient\applications\appinfo.db, 
access=c000, rc=ok
OPEN file=2C, name=D:\blp\wintrv\smartclient\applications\appinfo.db, 
access=c000, pOutFlags=12F09C, *pOutFlags=2, rc=ok
FCNTL file=2C, op=18, pArg=12EE94
FCNTL file=2C, rc=SQLITE_OK
FCNTL file=2C, op=18, pArg=12F078
FCNTL file=2C, rc=SQLITE_OK
READ file=2C, buffer=12F2C8, amount=100, offset=0, lock=0
READ file=2C, rc=SQLITE_OK
FCNTL file=2C, op=15, pArg=214BB8
FCNTL file=2C, rc=SQLITE_NOTFOUND
FCNTL file=2C, op=18, pArg=12F044
FCNTL file=2C, rc=SQLITE_OK
FCNTL file=2C, op=14, pArg=12EB64
FCNTL file=2C, rc=SQLITE_NOTFOUND
LOCK file=2C, oldLock=0(0), newLock=1
READ-LOCK file=2C, lock=0
READ-LOCK file=2C, rc=SQLITE_ERROR
LOCK file=2C, lock=1, rc=SQLITE_OK
ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.db-journal, flags=0, 
pResOut=12DDA8
ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.db-journal, 
pResOut=12DDA8, *pResOut=0, rc=SQLITE_OK
SIZE file=2C, pSize=12DCB4
SIZE file=2C, pSize=12DCB4, *pSize=1024, rc=SQLITE_OK
ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.db-wal, flags=0, 
pResOut=12DDB8
ACCESS name=D:\blp\wintrv\smartclient\applications\appinfo.db-wal, 
pResOut=12DDB8, *pResOut=0, rc=SQLITE_OK
SIZE file=2C, pSize=12DDB0
SIZE file=2C, pSize=12DDB0, *pSize=1024, rc=SQLITE_OK
READ file=2C, buffer=3DFEC8, amount=1024, offset=0, lock=1
READ file=2C, rc=SQLITE_OK
OPEN name=D:\blp\wintrv\smartclient\applications\appinfo.db-wal, pFile=215BD8, 
flags=80006, pOutFlags=12DD14
OPEN file=30, name=D:\blp\wintrv\smartclient\applications\appinfo.db-wal, 
access=c000, rc=ok
OPEN file=30, name=D:\blp\wintrv\smartclient\applications\appinfo.db-wal, 
access=c000, pOutFlags=12DD14, *pOutFlags=2, rc=ok
FCNTL file=2C, op=18, pArg=12DD34
FCNTL file=2C, rc=SQLITE_OK
OPEN name=D:\blp\wintrv\smartclient\applications\appinfo.db-shm, pFile=3E0398, 
flags=80006, pOutFlags=0
OPEN file=34, name=D:\blp\wintrv\smartclient\applications\appinfo.db-shm, 
access=c000, rc=ok
OPEN file=34, name=D:\blp\wintrv\smartclient\applications\appinfo.db-shm, 
access=c000, pOutFlags=0, *pOutFlags=0, rc=ok
SHM-LOCK file=34, lock=3, offset=128, size=1
SHM-LOCK file=34, func=winLockFile, errno=0, rc=SQLITE_OK
TRUNCATE file=34, size=0, lock=0
SEEK file=34, offset=0
SEEK file=34, rc=SQLITE_OK
TRUNCATE file=34, rc=SQLITE_OK
SHM-LOCK file=34, lock=1, offset=128, size=1
SHM-LOCK file=34, func=winUnlockFile, errno=0, rc=SQLITE_OK
SHM-LOCK file=34, lock=2, offset=128, size=1
SHM-LOCK file=34, func=winLockFile, errno=0, rc=SQLITE_OK
SIZE file=34, pSize=12D74C
SIZE file=34, pSize=12D74C, *pSize=0, rc=SQLITE_OK
SHM-LOCK file=34, lock=3, offset=120, size=1
SHM-LOCK file=34, func=winLockFile, errno=0, rc=SQLITE_OK
SHM-LOCK pid=2776, id=0, sharedMask=000, exclMask=001, rc=SQLITE_OK
SIZE file=34, pSize=12D74C
SIZE file=34, pSize=12D74C, *pSize=0, rc=SQLITE_OK
TRUNCATE file=34, size=32768, lock=0
SEEK file=34, offset=32768
SEEK file=34, rc=SQLITE_OK
LOG: os_win.c:33842: (33) 
winTruncate2(D:\blp\wintrv\smartclient\applications\appinfo.db-shm) - 
ãƒ—ãƒã‚»ã‚¹ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“ã€‚åˆ¥ã®ãƒ—ãƒã‚»ã‚¹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã®ä¸€éƒ¨ã‚’ãƒãƒE‚¯ã—ã,
 extended-result-code: 1546
TRUNCATE file=34, rc=SQLITE_IOERR_TRUNCATE
LOG: os_win.c:35002: (33) 
winShmMap2(D:\blp\wintrv\smartclient\applications\appinfo.db) - 
ãƒ—ãƒã‚»ã‚¹ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“ã€‚åˆ¥ã®ãƒ—ãƒã‚»ã‚¹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã®ä¸€éƒ¨ã‚’ãƒãƒE‚¯ã—ã¦ãE,
 extended-result-code: 4874
SHM-LOCK file=34, lock=1, offset=120, size=1
SHM-LOCK file=34, func=winUnlockFile, errno=0, rc=SQLITE_OK
SHM-LOCK pid=2776, id=0, sharedMask=000, exclMask=000, rc=SQLITE_OK
LOG: disk I/O error, extended-result-code: 4874
Error occurred-> SQLITE_IOERR[10]: disk I/O error
LOCK file=2C, oldLock=1(0), newLock=4
READ-UNLOCK file=2C, lock=1
READ-UNLOCK file=2C, rc=SQLITE_ERROR
LOCK file=2C, lock=4, rc=SQLITE_OK
SIZE file=34, pSize=12EA4C
SIZE file=34, pSize=12EA4C, *pSize=0, rc=SQLITE_OK
SIZE file=34, pSize=12EA4C
SIZE file=34, pSize=12EA4C, *pSize=0, rc=SQLITE_OK
TRUNCATE file=34, size=32768, lock=0
SEEK file=34, offset=32768
SEEK file=34, rc=SQLITE_OK
LOG: os_win.c:33842: (33) 
winTruncate2(D:\blp\wintrv\smartclient\applications\appinfo.db-shm) - 
ãƒ—ãƒã‚»ã‚¹ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“ã€‚åˆ¥ã®ãƒ—ãƒã‚»ã‚¹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã®ä¸€éƒ¨ã‚’ãƒãƒE‚¯ã—ã,
 extended-result-code: 1546
TRUNCATE file=34, rc=SQLITE_IOERR_TRUNCATE
LOG: os_win.c:35002: (33) 
winShmMap2(D:\blp\wintrv\smartclient\applications\appinfo.db) - 
ãƒ—ãƒã‚»ã‚¹ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“ã€‚åˆ¥ã®ãƒ—ãƒã‚»ã‚¹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã®ä¸€éƒ¨ã‚’ãƒãƒE‚¯ã—ã¦ãE,
 extended-result-code: 4874
SHM-PURGE pid=2776,

Re: [sqlite] How to Troubleshoot Disk I/O Error

2014-02-20 Thread Dan Kennedy


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.




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


___
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

2014-02-20 Thread Simon Slavin

On 20 Feb 2014, at 2:29pm, 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 ?

Have you checked the media for faults ?  In other words, I'm suggesting you 
check for a hardware failure.  Try copying the whole database file from it 
using conventional copy commands.

Also check for corruption of the database using "PRAGMA integrity_check"

Simon.
___
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

2014-02-20 Thread Akintoye Olorode (BLOOMBERG/ 731 LEXIN)

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

2014-01-30 Thread Teg

Hello Akintoye,

A common problem I ran into with the transition from XP to anything
newer is that the user folders changed. So, what was a legal
read/write folder in XP wasn't in Vista+. I had the folder embedded in
the  configuration file so, when they brought their old configurations
forward, they were pointed at the wrong folder.

Easy way to determine if this is the case it to right click the
application and "Run as Administrator". If it starts working then you
know the problem is permissions.

For my users, the choice is to move the file, change the permissions,
re-install  or just "Run as Administrator" (which I suggested they not
do).

Thursday, January 30, 2014, 10:52:18 AM, you wrote:

AOB7L> Thanks, will try this suggestions and post results.

AOB7L> - Akintoye

AOB7L> - Original Message -
AOB7L> From: sqlite-users@sqlite.org
AOB7L> To: sqlite-users@sqlite.org
AOB7L> At: Jan 30 2014 10:44:45

AOB7L> 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.

AOB7L> Immediately after the error occurs, what value is returned by
AOB7L> the sqlite3_extended_errcode() function? Often the extended error
AOB7L> code identifies the specific IO operation that failed, which can
AOB7L> shed light on the problem.

AOB7L> Another thing to do is to try compiling with the following defines:

AOB7L>-DSQLITE_DEBUG=1 -DSQLITE_DEBUG_OS_TRACE=1

AOB7L> This causes the Windows VFS module to print various messages to
AOB7L> standard output that should help to figure out what is happening.

AOB7L> Dan.

AOB7L> ___
AOB7L> sqlite-users mailing list
AOB7L> sqlite-users@sqlite.org
AOB7L> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

AOB7L> ___
AOB7L> sqlite-users mailing list
AOB7L> sqlite-users@sqlite.org
AOB7L> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

-- 
Best regards,
 Tegmailto:t...@djii.com

___
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

2014-01-30 Thread Akintoye Olorode (BLOOMBERG/ 731 LEXIN)

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

2014-01-30 Thread Akintoye Olorode (BLOOMBERG/ 731 LEXIN)

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

2014-01-30 Thread Dan Kennedy


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

Re: [sqlite] How to Troubleshoot Disk I/O Error

2014-01-30 Thread Dan Kennedy


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 is 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

Re: [sqlite] How to Troubleshoot Disk I/O Error

2014-01-30 Thread Stephen Chrzanowski

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) <
aolor...@bloomberg.net> 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

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

Re: [sqlite] How to Troubleshoot Disk I/O Error

12 matches

Site Navigation

Mail list logo

Footer information