title: Unable to upgrade SVN working copy
body: <p>I have a very very large svn repo.  When I try to use it (commit, update, etc.) it says there are locks.</p>
  
  <p>When I run 'svn cleanup', it says that the working copy is too old and I need to upgrade it.</p>
  
  <p>When I run 'svn upgrade', it runs, but doesn't say anything.</p>
  
  <p>I also ran 'svnadmin upgrade' on the repo, just in case.</p>
  
  <p>I have the latest TortoiseSVN installed.</p>
  
  <p>Normally, if I had SVN weirdness, I'd move the files out, update, move the files back, but as I mentioned earlier, this is a very LARGE repo.</p>
  
  <p>Any help would be appreciated.</p>
  
  <p>Thanks!</p>
  
  <p>Specific messages:</p>
  
  <pre><code>&gt;svn update
  svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
  svn: E155004: Working copy '*****' locked.
  svn: E155004: '*****' is already locked.
  
  &gt;svn cleanup
  svn: E155036: Please see the 'svn upgrade' command
  svn: E155036: The working copy at '*****' is too old (format 29) to work with client version '1.8.1 (r1503906)' (expects format 31). You need to upgrade the working copy first.
  
  &gt;svn upgrade
  
  &gt;
  </code></pre>
  
  <p><strong>Update 1</strong>:
  I installed a 1.7.X client and tried to run a cleanup.  It complained that the repo wasn't a working copy, for some reason.  I tried an update with the same 1.7.X client and got the following message:</p>
  
  <pre><code>&gt;"c:\Program Files\SlikSvn\bin\svn.exe" update
  svn: E155021: This client is too old to work with the working copy at '*****' (format 31).
  You need to get a newer Subversion client. For more details, see http://subversion.apache.org/faq.html#working-copy-format-change
  </code></pre>
  
  <p>So, this client things the repo is format 31.  The tortoisesvn thinks it is format 29.  Now I'm more confused.</p>
  
  <p><strong>Update 2</strong>:
  Response to @David W</p>
  
  <pre><code>Is this about a working copy or the repository?
  </code></pre>
  
  <p>Working copy.  Though I tried svnadmin upgrade on the repo as well.  However, the svnadmin I used was the 1.8.1.  I just tried to upgrade the repo with the TortoiseSVN one (1.8.10), but that didn't fix the issue.</p>
  
  <pre><code>is this about a file that's locked because someone locked it, or because your working directory is locked due to an incomplete
  </code></pre>
  
  <p>I'm the only one using the repo, so I know no one else locked it.  Its probably due to an incomplete op.</p>
  
  <p>I ran svn status with 1.8.10, and nothing had a 'K'.  There were some files with an 'L', and one with a '?'.  All items listed were directories, not files, with the exception of the one marked with a '?'.</p>
  
  <p>If I ran an 'svn lock --force dirname', it would respond that that specific node "is not a file".  When I ran it on the file marked with a '?', it responded that that node 'was not found'.</p>
  
  <pre><code>Then, there is a locked working directory because of an incomplete operation...
  </code></pre>
  
  <p>Yep, you called it.  That is why all the things are marked with an 'L', I gather.</p>
  
  <p>When I ran a cleanup (1.8.10) it gave me the same error I reported in my intiial question (format 29 too old for this format 31 client).</p>
  
  <pre><code>Remember that you can always delete a working directory and create a new one
  </code></pre>
  
  <p>Yep.  If I delete any directory in the working copy and hit update, it complains that it is locked.  I can't clear the lock, 'cause of the format mismatch. I can theoretically just re-checkout the entire repo, then copy things back, but the repo is 12GB (210,000 files).</p>
  
  <pre><code>Be careful about mixing up Subversion clients
  </code></pre>
  
  <p>So, I was unaware that I had two clients, but I only only only use TortoiseSVN (1.8.10).  I only discovered today that I had two when I was trying to troubleshoot.</p>
  
  <p><strong>* UPDATE 3: RESOLUTION *</strong>
  Using @David W's tips, here is how I fixed the problem:
  1) Backed up my .svn folder
  2) Downloaded an SQLite editor from <a href="https://github.com/sqlitebrowser/sqlitebrowser/releases" rel="noreferrer">https://github.com/sqlitebrowser/sqlitebrowser/releases</a>
  3) Opened up my wc.db file and browsed the WC_LOCK table. There was 1 entry in that table, which I removed.
  4) Tried running a cleanup using TortoiseSVN (1.8.10), which previously complained about locks. It finally worked!
  5) Tried running commands in my repo (update, commit, etc.), and everything was happy.</p>
  
  <p>Thank you to everyone who helped, especially @David W for not giving up on me.</p>