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

svn doesn't recognize the working copy when no file lock can be established

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8.x
    • Fix Version/s: ---
    • Component/s: libsvn_ra_local
    • Labels:
      None

      Description

      The issue manifests itself when, for example, subversion repository is shared 
      over NFS and file lock through fcntl(fd,F_SETLK) fails with (Operation not 
      supported).
      
      In this case 'svn info' command prints this error message on otherwise valid 
      working copy:
      svn: E155007: '/usr/src' is not a working copy
      
      Subversion should recognize this situation when only lock fails but working copy 
      is otherwise valid. Subversion should access it read-only and warn user that 
      transient errors can occur in case other read-write accesses happen at the same 
      time.
      
      My usage example: I have the local working copy for FreeBSD source, and share it 
      with several virtual machines through NFS. They rarely, if ever, access it 
      through 'svn' comamnd simultaneously. read-only vs. read-write conflicts never 
      occur, yet I am unable to use svn commands on NFS share at all. SVN revision is 
      missing from all builds on virtual machines.
      
      I believe, the failing fcntl command is issued by SQLite library.
      
      subversion-1.8.1
      

      Original issue reported by yurivict

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              subversion-importer Subversion Importer
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: