Actions
Bug #20593
closedmds: the number of inode showed by "mds perf dump" not correct after trimming
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Performance/Resource Usage
Target version:
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
currently, mds only update the inode number for "mds perf dump" in function "MDSRank::_dispatch"
this means it will only be updated when there is a client request.
this will cause "mds perf dump" show a wrong inode number after mds trimming the inode when there is no client requst comming yet.
i have already pulled a requst to try to solve this issue:
Updated by Patrick Donnelly almost 7 years ago
- Status changed from New to Fix Under Review
Updated by Patrick Donnelly about 6 years ago
- Subject changed from the number of inode showed by "mds perf dump" not correct after trimming to mds: the number of inode showed by "mds perf dump" not correct after trimming
- Category set to Performance/Resource Usage
- Status changed from Fix Under Review to Pending Backport
- Assignee set to dongdong tao
- Target version set to v13.0.0
- Source set to Community (dev)
- Backport set to luminous
- Component(FS) MDS added
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23642: luminous: mds: the number of inode showed by "mds perf dump" not correct after trimming added
Updated by Nathan Cutler almost 6 years ago
- Status changed from Pending Backport to Resolved
Master commit was included in the initial luminous v12.2.0 release:
$ git describe 27e7cda322547b820cc5c0b5443c3dbbb4897e80 v12.1.0-694-g27e7cda322
Updated by Nathan Cutler almost 6 years ago
Sorry, should have used the PR#16232 merge commit.
$ git describe 11d809e9fe85cf2b1d5c1ff70245aa4d02c4bfdd v12.1.1-352-g11d809e9fe
Actions