I'm getting intermittent errors like this when doing svn update
from the command line.
svn: E200030: sqlite[S10]: disk I/O error
svn: E200033: Another process is blocking the working copy database, or the
underlying filesystem does not support file locking; if the working copy is
on a network filesystem, make sure file locking has been enabled on the file
server
svn: E200033: sqlite[S5]: database is locked, executing statement 'PRAGMA
synchronous=OFF;PRAGMA recursive_triggers=ON;PRAGMA foreign_keys=OFF;PRAGMA
locking_mode = NORMAL;'
I'm having a hard time figuring out if they are coming from my local machine or from the svn server. I have found some indications online that these types of messages may be local and caused by TortoiseSVN.
Other devs on my team don't seem to get these errors. Could it be that it's not supported to use svn from the command line while TortoiseSVN is running? (I don't think other devs on my team do that, only me... my main use of the command line is to run a batch file that updates all of my svn working folders so I don't have to update them one by one)
Those are coming from your machine. SVN since version 1.7 has used a SQLite database for the working copy pristines and metadata (the .svn
folder in your working copy). The server uses just the bare file system.
I've never seen these, but I could see how running a TortoiseSVN operation at the same time as a command line SVN command might cause this. They'd both attempt to access the .svn
folder and the SQLite database inside it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With