Hi, Dr. Hartmut, Thank for your tips, but the problem in my company was the type of filesystem that I use for the build the SVN project. After this, I changed and I migrated the repositories and don't happened again, but I agree with your tip and I go to verify this possibility and stay attent.
Thanks lot, JC 2013/2/1 Niemann, Hartmut <hartmut.niem...@siemens.com> > I have seen random client-side disk IO errors when our virus scanner > interfered with the > sqlite library used in subversion 1.7, when massive log file activity > triggered a bug > (which is still not fixed) in the behavioural analysis module of the virus > scanner. > > Try to disable the virus scanner (at least for the .svn directory) > or try a subversion 1.6 client which does not use sqlite. > > I can send you some detailed information and a test application if you are > interested. > > > > Mit freundlichen Grüßen > Dr. Hartmut Niemann > > > > ________________________________ > > Von: Julio Palma [mailto:ju...@sigcorp.com.br] > Gesendet: Donnerstag, 24. Januar 2013 21:44 > An: users@subversion.apache.org > Betreff: Commit Error in conversion of types > > > Hi, Subversion community, > > > [...] > 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 > > [...] > > > >
