Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

Switch to latest✕

Replace a failed Ceph OSD with a metadata device

Warning

This procedure is valid for MOSK clusters that use the MiraCeph custom resource (CR), which is available since MOSK 25.2 to replace the unsupported KaaSCephCluster resource. And MiraCeph will be automatically migrated to CephDeployment in MOSK 26.1. For details, see Deprecation Notes: KaaSCephCluster API on management clusters.

For the equivalent procedure with the unsupported KaaSCephCluster CR, refer to the following section:

Replace a failed Ceph OSD with a metadata device

The document describes various scenarios of a Ceph OSD outage and recovery or replacement. More specifically, this section describes how to replace a failed Ceph OSD with a metadata device:

• If the metadata device is specified as a logical volume in the BareMetalHostProfile object and defined in the MiraCeph object as a logical volume path

• If the metadata device is specified in the MiraCeph object as a device name

Note

Ceph OSD replacement implies the usage of the CephOsdRemoveRequest custom resource (CR). For workflow overview, spec and phases description, see High-level workflow of Ceph OSD or node removal.

• Replace a failed Ceph OSD with a metadata device as a logical volume path
  • Remove a failed Ceph OSD by ID with a defined metadata device
  • Re-create a Ceph OSD with the same metadata partition
• Replace a failed Ceph OSD disk with a metadata device as a device name
  • Remove a Ceph OSD with a metadata device as a device name
  • Re-create the metadata partition on the existing metadata disk
  • Re-create the Ceph OSD with the re-created metadata partition