Details

    • Type: Improvement
    • Status: To Do (View workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: None
    • Labels:
      None
    • Sprint:

      Description

      the locking mechanism has benn changed such that if the file system operation contains inodeID then the ID is used to lock the inode and the path is resoved in reverse using the cache. There is no guarantee that the case will have all the inodes in the path.

      I my opinion the correct behavious should be lock the inode using path and if the path is not valid then INodeID should be used. I need to look more in to this soulution.

        Attachments

          Activity

            People

            • Assignee:
              smkniazi Salman Niazi
              Reporter:
              smkniazi Salman Niazi
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: