Svn: E155004: Working copy '/./svn-site' locked. Svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) Running "svn cleanup" after discovering a lost pristine does not help, and in fact makes things *worse* because it locks the WC which previously was not locked. For example, here are three reports that also include useful information and suggestions for fixing the WC: Other people have run into the same situation. The bug may or may not still exist in 1.8.x stabilization, but as far as I know, no such bug has been identified and fixed, so I would assume the bug probably still does exist. The bug may have been triggered by some exceptional condition such as network failure during 'svn update'. My best guess is it was caused by a bug in a (development) version of Subversion that I was using on this working copy at some point in the past, that set the ref-count column to 0 erroneously, and then a subsequent 'svn cleanup' removed the pristine. Some of the pristine texts referenced by the wc.db 'nodes.checksum' column were missing from the wc.db 'pristine' table and from the '.svn/pristine/' directory. I have just been fixing one of my WCs, in which a number of pristine texts had gone missing from the pristine store.