Actions
Bug #12222
closedMDSMonitor: set max_mds doesn't respect MAX_MDS
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
new_dev
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Various allocation ranges are calculated based on MAX_MDS, but we don't actually stop the user from creating more MDSs than that!
Actions