On 6 July 2012 09:04, Stefan Fuhrmann <stefan.fuhrmann_at_wandisco.com> wrote:
> On Fri, Jul 6, 2012 at 12:58 AM, Neels J Hofmeyr <neels_at_elego.de> wrote:
>> Today Random Person on #svn reported a problem and later its apparent
>> solution, and it struck me as rather peculiar:
>> <yates`> when trying to do an svn cleanup, i get a strange message:
>> svn: E200030: disk I/O error, executing statement 'COMMIT TRANSACTION;'
> I suspect a reader / writer locking issue with Sqlite.
> The I/O error as such might be related to the win7 /
> cygwin combination requiring more retries or such.
>> this is under win7 using the cygwin svn client
>> and also tortoisesvn is installed
>> <yates`> neels: i found the issue
>> strangely, there is an interaction between tortoisesvn and the cli svn
>> you must disable tortoisesvn's icon caching, then the problem goes away.
> I.e. they disabled the background process that will
> open the working copy soon after the OS detected
> some file change. The scan itself may take a very
> long time. Depending on OS and wc details, the db
> may get opened at some very inconvenient time
> while the commit is still in progress / in some critical
>> "I've confirmed what others have stated that it's only a problem with
>> v18.104.22.168 and NOT a problem with v3.7.3."
>> Hmm, disable icon caching to not break wc-ng? Why!?
> I think to remember that access to WCNG is much
> more exclusive than it used to be in 1.6. But I don't
> know whether that is actually true not the details.
In our FAQ we advise against using TortoiseSVN with CygWin because
Subversion was never designed to share a working copy between Windows
and *nix clients. I thought this was in the SVN FAQ too, but can't
find it right now.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
Received on 2012-07-06 14:21:25 CEST