Hello there, I have a couple related questions:
1) Is anyone aware of any recent cases of SQLite DB corruption? We upgraded from SQLite 3.3.6 to SQLite 3.4.1 a few months ago. In the last couple days, we've encountered a couple cases of SQLite reporting that a DB file had become corrupted ("database disk image is malformed"). I believe that both cases involved writing to NFS. However, we use our own locking mechanism to handle some faulty NFS implementations regarding locking and fcntl().
In one case, only a single (unthreaded) process was accessing the database over NFS. However, that process was running in a Linux VMware virtual machine. Less is known about the other case, but it was also running in Linux (not running in a VM) while writing to NFS. Both cases involve NetApp boxes (but not the same one).
Aside from NFS locking issues, I'm not aware of any issues involving SQLite and NFS. Since one case didn't involve concurrency, perhaps there's another problem.
2) In order to help diagnose the problem, we ran some unit tests, and we had some unusual results:
a) On a native Linux/x86 system, the lock4-1.3 test for SQLite 3.4.1 will fail intermittently, both on NFS and local disk. Is the test not very robust? Perhaps there's a race condition?
b) On a native Linux/AMD64 system, the io-4.2.2 test for SQLite 3.5.2 will fail regularly on both local disk and NFS. Is this cause for concern?
c) On a Linux/x86 VM (running under Windows), some tests fail. I don't have the specifics at the moment, but that would be cause for alarm, particularly the failures are above (a) and (b), assuming those are not problematic.
Thanks, Arun ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
