It appears to be a problem with the client on Windows. Subversion uses SQLite to access .svn/wc.db in the working copy and it appears to be failing. I don't know much about debugging on Windows.
How did you create the working copy? Can you checkout a new working copy? Is your working copy on some sort of network disk? SVNKit is a Java reimplementation of Subversion; perhaps it has a bug in it's SQLite implementation. Can you try a client based on the C libraries (TortoiseSVN or svn)? Julio Palma <ju...@sigcorp.com.br> writes: > Hi, Philip, > > Thank you for your awnsers, but the error persists, I do like you was > recommend, but after reload and synchronize the error persists. > > My configuration in the server is?: > > Linux Ubuntu Server > > My clients are windows 7 and 8 with eclipse subversive + SVNKit 1.7.6 > > Thank Lot, > > JC > > > 2013/1/25 Philip Martin <philip.mar...@wandisco.com> > >> Julio Palma <ju...@sigcorp.com.br> writes: >> >> > My name is Julio Cesar, I made a configuration a Subversion server in a >> > Ubuntu Linux, and I have a Lot of troubles with encoding format from my >> > archives sources, some sources are write on windows-1252 and when I >> > submit/commit, the files given me a error like described: >> > >> > Some of selected resources were not committed. >> > Some of selected resources were not committed. >> > svn: E200030: Commit failed (details follow): >> > svn: E200030: Commit failed (details follow): >> > svn: E200030: disk I/O error >> > svn: E200030: disk I/O error >> > svn: E200029: Couldn't perform atomic initialization >> > >> > Searching on the web, I dont have any source of information about this, >> and >> > I need to do maintenance at many sources with the same problem. >> > >> > I need to know: >> > >> > 1. Exists one way to convert this files with a svn command? >> > 2. It is a permission problem? >> > 3. or both? >> > >> > >> > One way that I do for fix it, was use linux shell, in the follow >> sequence : >> > >> > 1. convert the file with iconv command: >> > "iconv -c -f WINDOWS-1252 -t UTF-8 file.php > newfile.php | mv file.php >> > file.php_old | newfile.php file.php" >> > >> > 2. "Checkout" from the folder from original revision, I move the file.php >> > and rewrite the same file.php and follow a "svn commit", then the source >> > finish with sucess. >> > >> > I need to fix it's in my repository, from one way that will be clean and >> > safe. >> >> The error numbers are: >> >> 00200030 SVN_ERR_SQLITE_ERROR >> 00200029 SVN_ERR_ATOMIC_INIT_FAILURE >> >> I think that is a problem accessing .svn/wc.db in your working copy, the >> file is corrupt or unreadable or something. I've never seen that error >> before. Do you still have the working copy? Can you reproduce the >> error? >> >> Subversion does not care about the encoding of file.php in the >> repository, it can handle files in any encoding. >> >> -- >> Certified & Supported Apache Subversion Downloads: >> http://www.wandisco.com/subversion/download >> -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
