[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Corrupt working copies with Subversion 1.7.4 in VMWare with shared folders (two svn processes; malformed sqlite database)

From: Florian Kolter <fk_at_floriankolter.de>
Date: Mon, 23 Apr 2012 17:07:15 +0200

Hi Markus,

* Markus Schaber [2012-04-23 14:53]:
> Hi, Florian,
> Von: Florian Kolter [mailto:fk_at_floriankolter.de]
> >
> > since upgrading svn from 1.6.16 (TortoiseSVN 1.6.15) to 1.7.4 (TortoiseSVN
> > 1.7.6) my working copies are very often corrupted and clean up can't
> > recover them. Unfortunately this happens sporadically and I can't
> > reproduce it with a demo repository. But maybe you have an idea.
> >
> > I'm working inside a VMWare image, accessing the host's working copies
> > using shared folders. I must not change this special setup.
> >
> > Can two TSVNCache processes accessing the same working copy (SQLite
> > database) produce any damage? SVN 1.6.x worked just fine.
> Accessing the same working copy from several processes works fine as long as the locking works fine.
> However, locking over network file systems has issues in some cases, and VirtualBox uses network file system emulation for the shared folders for windows guests.
> So my hint is that you check with the VirtualBox folks whether they know of any issues with locking on shared folders. (Maybe simply updating VirtualBox or the guest utils helps. :-)

Thanks for your tip. I can try to find out what VMWare's implementation
does or if there is an update.

However I have been working this way for years with Subversion 1.6 and
never experienced any problem. Was this kind of locking introduced in
Subversion 1.7? Because of SQLite?

Best regards,
Received on 2012-04-23 17:08:13 CEST

This is an archived mail posted to the Subversion Users mailing list.