Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-4989

nodemap: only cancel affected locks on export

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Low Priority
    • Affects Version/s: Lustre 2.7.0
    • Fix Version/s: None
    • Labels:
    • Rank (Obsolete):
      13820

      Description

      Per previous discussion, filing a bug here to track this improvement for the future. When cancelling locks in member_revoke_locks() (added in patch http://review.whamcloud.com/9299) it makes sense to optimize this to only cancel locks on the export that are actuall affected by the change to the idmap (e.g. UID/GID being removed/changed, or node being removed from the idmap or nodemap).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wc-triage WC Triage
                Reporter:
                adilger Andreas Dilger
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: