Feature #51340
closedmon/MDSMonitor: allow creating a file system with a specific fscid
0%
Description
In the scenario where the monitor databases are lost and must be rebuilt, the file system will need recreated. (Assuming pools have been recovered by OSDMap reconstruction from the incremental OSDMaps on the OSDs.) Some external projects like ceph-csi reasonably expect the fscid to be stable. During this recovery scenario, the fscid will likely change back to the default starting value (0 or 1).
Allow the administrator to set the fscid via the "fs new" command. If no existing file system exists with that fscid, allow it. (This breaks the "rule" that fscids for "new" file systems are always increasing. We should note this exception in the documentation!)
Updated by Ramana Raja almost 3 years ago
- Status changed from New to In Progress
- Pull request ID set to 42106
Updated by Ramana Raja almost 3 years ago
- Status changed from In Progress to Fix Under Review
Updated by Patrick Donnelly almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51834: pacific: mon/MDSMonitor: allow creating a file system with a specific fscid added
Updated by Loïc Dachary over 2 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".