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

[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