Verification of cStor Storage Pool
cStor Storage Pool(CSP) resources are cluster scoped resources. Status of CSPs can be obtained using the following way.
kubectl get csp
Example output:
NAME ALLOCATED FREE CAPACITY STATUS TYPE AGE
cstor-disk-pool-g5go 270K 9.94G 9.94G Healthy striped 2m
cstor-disk-pool-srj3 270K 9.94G 9.94G Healthy striped 2m
cstor-disk-pool-tla4 270K 9.94G 9.94G Healthy striped 2m
Status of each cStor pool can be found under STATUS field.
Note: Status of CSPs are updated only if its corresponding cStor pool pod is Running.
The following are the different type of STATUS information of cStor pools and their meaning.
Healthy: This state represents cStor pool is online and running.
Offline: cStor pool status is offline due to the following cases:
- when pool creation or pool import is failed.
- when a disk is unavailable in case of the pool is created in a striped manner.
- when tampering happens on CSP resource and invalid values are set then CSP will be updated to offline.
Degraded: cStor pool status is degraded due to the following cases:
- when any one of the disks is unavailable on the node where the pool is created either Mirror, Raidz or Raidz2 manner.
Error: This means cstor-pool container in cStor pool pod is not in running state.
DetetionFailed: There could be an internal error occurred when CSP is deleted.
Note: If the target pod of corresponding cStor volume is not running, then the status of cStor volume shown in the output of the above command may be stale.
Verification of cStor Volume
cStor Volume is namespace scoped resource. You have to provide the same namespace where openebs is installed. Status of cStor Volume can be obtained using the following way.
kubectl get cstorvolume -n <openebs_installed_namespace>
Example command:
kubectl get cstorvolume -n openebs
Example output:
NAME STATUS AGE CAPACITY
pvc-4c3baced-c020-11e9-ad45-42010a8001c8 Healthy 1h 5G
Status of each cStor volume can be found under STATUS field.
Note: If the target pod of corresponding cStor volume is not running, then the status of cStor volume shown in the output of the above command may be stale.
The following are the different type of STATUS information of cStor volumes and their definition.
Init: Init status of cStor volume is due to the following cases:
- when the cStor volume is created.
- when the replicas are not connected to target pod.
Healthy: Healthy status of cStor volume represents when 51% of replicas are connected to the target and it represents volume is ready for processing IOs.
Degraded: All replicas of the cStor volume are not in Healthy state, the corresponding volume will be running as degraded. In this case, IOs can happen on this volume.
Offline: Replicas may not able to connect to its target pod due to network issues. In this case, IOs will not happen on this cStor volume.
Verification of cStor Volume Replica
cStor Volume Replica is namespace scoped resource. You have to provide the same namespace where openebs is installed. Status of cStor Volume Replica can be obtained using the following way.
kubectl get cvr -n <openebs_installed_namespace>
Example command:
kubectl get cvr -n openebs
Example output:
NAME USED ALLOCATED STATUS AGE
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-g5go 6K 6K Offline 21s
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-srj3 6K 6K Offline 21s
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-tla4NAME USED ALLOCATED STATUS AGE
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-g5go 6K 6K Offline 21s
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-srj3 6K 6K Offline 21s
pvc-4c3baced-c020-11e9-ad45-42010a8001c8-cstor-disk-pool-tla4 6K 6K Offline 21s 6K 6K Offline 21s
Status of each cStor volume Replica can be found under STATUS field.
Note: If the target pod of corresponding cStor volume replica is not running, then the status of CVR shown in the output of the above command may be stale.
The following are the different type of STATUS information of cStor Volumes Replica and their definition.
Healthy: Healthy state represents volume is healthy and volume data existing on this replica is up to date.
Offline: cStor volume replica status is offline due to the following cases:
- when the corresponding cStor pool is not available to create volume.
- when the creation of cStor volume fails.
- when the replica is not yet connected to the target.
Degraded: cStor volume replica status is degraded due to the following case
- When the cStor volume replica is connected to the target and rebuilding is not yet started on this replica.
Rebuilding: cStor volume replica status is rebuilding when the cStor volume replica is undergoing rebuilding, that means, data sync with another replica.
Error: cStor volume replica status is in error state due to the following cases:
- when the volume replica data set is not existing in the pool.
- when an error occurs while getting the stats of cStor volume.
DeletionFailed: cStor volume replica status is deletion failed while destroying cStor volumes fails.
Invalid: cStor volume replica status is invalid when a new cstor-pool-mgmt container in a new pod is communicating with the old cstor-pool container in an old pod.
Init: cStor volume replica status init represents the volume is not yet created.
Recreate: cStor volume replica status recreate represents an intermediate state before importing the volume(this can happen only when pool pod got restarted) in case of a non-ephemeral disk. If the disk is ephemeral then this status represents volume is going to recreate.