title: SVN working copy has all sorts of database etc. problems
body: <p>We have SVN working copies of three websites held on a development server in the office. The server WAS Linux, and the working copies were worked on Windows machines and updated / committed etc. using TortoiseSVN. I will preface this by saying that I know working copies on network shares aren't strictly supported, but it was done this way so that we could test our code changes to the sites offline on local dev URLs before putting them on the live server.</p>
  
  <p>This WAS working absolutely brilliantly. No problems at all - until our Linux server developed problems and had to be replaced. We have replaced it with a Mac to kill the second bird of having a Mac in-house for browser testing.</p>
  
  <p>Ever since moving everything to the Mac, SVN has been extremely problematic. Commits / updates often fail with "database is locked" errors, and I cannot do clean up most of time as it usually fails with this error:</p>
  
  <p>Cleanup failed to process the following paths:
  PATH TO WC ON NETWORK
  database is locked, executing statement 'COMMIT TRANSACTION;'</p>
  
  <p>The statement being executed differs, sometimes being something to do with RELEASE.</p>
  
  <p>The code changes we are making must be tested on our dev server before being committed to the live site online. As it stands, I now have a working copy checked out on my own hard drive. I have to commit my changes, update on the development server (and pray it works - it takes AGES either way) and test them, before then updating the live server if they work.</p>
  
  <p>I cannot checkout new working copies on the network share either - again, it usually fails complaining of a disk I/O error, or a database becoming locked. We have already disabled all the Mac's power saving functions in case a sleep or hard disk spindown was responsible - no luck.</p>
  
  <p>I would prefer to keep the working copy on the network share if possible. As I've already said, I realise it's not the most suitable way to do SVN but it's been working for us. What can I do to try and fix this problem? I suspect it's Windows -> Mac network related and actually have another question open about slow network access from my machine to the Mac network share.</p>