Project

General

Profile

Feature #36707

client: support getfattr ceph.dir.pin extended attribute

Added by Zhi Zhang about 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
luminous, mimic
Reviewed:
Affected Versions:
Component(FS):
Client, MDS
Labels (FS):
multimds
Pull request ID:

Description

In Multi-MDSes, we can set ceph.dir.pin on client to bind a directory to a specific MDS. But we can't get this attribute on client. So it is not convenient to check which directory is pinned on which MDS since we have multiple active MDSes running in a cluster and many user direcotires pinned to different MDS.


Related issues

Related to Linux kernel client - Feature #37576: support getting ceph.dir.pin attribute Resolved
Copied to CephFS - Backport #37636: mimic: client: support getfattr ceph.dir.pin extended attribute Rejected
Copied to CephFS - Backport #37637: luminous: client: support getfattr ceph.dir.pin extended attribute Rejected

History

#1 Updated by Patrick Donnelly about 4 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Zhi Zhang
  • Priority changed from Normal to High
  • Target version set to v14.0.0
  • Component(FS) Client, MDS added

#2 Updated by Patrick Donnelly about 4 years ago

  • Related to Feature #37576: support getting ceph.dir.pin attribute added

#3 Updated by Patrick Donnelly about 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Pull request ID set to 24940

#4 Updated by Nathan Cutler almost 4 years ago

  • Backport set to luminous, mimic

#5 Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #37636: mimic: client: support getfattr ceph.dir.pin extended attribute added

#6 Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #37637: luminous: client: support getfattr ceph.dir.pin extended attribute added

#7 Updated by Patrick Donnelly almost 4 years ago

  • Category deleted (90)

#8 Updated by Nathan Cutler almost 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF