Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-3430

write-lock stolen error at checkout time over svn+ssh

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 1.7.0
    • Component/s: libsvn_ra_svn
    • Labels:
      None

      Description

      From #svn-dev
      
      <stsp> svn: Write-lock stolen in ...
      <stsp> investigation suggests that this is a really bad problem?
      <stsp> as in a problem with the filesystem or something?
      <stsp> it happens to me on 2 different filesystems, though...
      <stsp> the place where this error is thrown has a comment saying:
      <stsp>    /* Check physical lock still exists and hasn't been stolen.  This
      <stsp>       really is paranoia, I have only ever seen one report of this
      <stsp>       triggering (from someone using the 0.25 release) and that was
      <stsp>       never reproduced. 
      <stsp> so I just reproduced it with trunk?
      <stsp> what are the odds of that? :)
      <stsp> do I win a trip to the moon?
      <stsp> hmm it's looking for a file called ".svn/lock" and that doesn't exist
      <stsp> 1.6.x works fine
      <stsp> wc-ng broke it?
      <hwright> that could be a wc-ng-related issue, yes.
      <hwright> do you have a repo script?
      <stsp> i can reproduce it only checking out from a private svn repo at elego so
      far :(
      <hwright> weird.  do you have the error stack trace? (or i
      s it an abort?)
      <stsp> I can trace
      <hwright>  the trace is interesting, indeed.  (it highlights a bug in our error
      tracing code)
      

        Attachments

        1. 1_issue-3430-trace.txt
          5 kB
          Stefan Sperling

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stsp Stefan Sperling
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: