What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?
Fault Locating
Troubleshooting methods are sorted based on the occurrence probability of the possible causes. You are advised to check the possible causes from high probability to low probability to quickly locate the cause of the problem.
If the fault persists after a possible cause is rectified, check other possible causes.
- Check Item 1: Whether EVS Volumes Are Mounted Across AZs
- Check Item 2: Whether Multiple Permission Configurations Exist in the Storage Volume
- Check Item 3: Whether There Is More Than One Replica for a Deployment with EVS Volumes
Check Item 1: Whether EVS Volumes Are Mounted Across AZs
Symptom
Mounting an EVS volume to a StatefulSet times out.
Fault locating
If your node is in AZ 1 but the volume to be mounted is in AZ 2, the mounting times out and the volume cannot be mounted.
Solution
Create a volume in the same AZ as the node and mount the volume.
Check Item 2: Whether Multiple Permission Configurations Exist in the Storage Volume
If the volume to be mounted stores too many data and involves permission-related configurations, the file permissions need to be modified one by one, which results in mounting timeout.
Fault locating
- Check whether the securityContext field contains runAsuser and fsGroup. securityContext is a Kubernetes field that defines the permission and access control settings of pods or containers.
- Check whether the startup commands contain commands used to query or modify file permissions, such as ls, chmod, and chown.
Solution
Determine whether to modify the settings based on your service requirements.
Check Item 3: Whether There Is More Than One Replica for a Deployment with EVS Volumes
Symptom
The pod fails to be created, and an event indicating that the storage fails to be added is reported.
Multi-Attach error for volume "pvc-62a7a7d9-9dc8-42a2-8366-0f5ef9db5b60" Volume is already used by pod(s) testttt-7b774658cb-lc98h
Fault locating
Check whether the number of replicas of the Deployment is greater than 1.
If the Deployment uses an EVS volume, the number of replicas can only be 1. If you specify more than two pods for the Deployment on the backend, CCE does not restrict the creation of the Deployment. However, if these pods are scheduled to different nodes, some pods cannot be started because the EVS volumes used by the pods cannot be mounted to the nodes.
Solution
Set the number of replicas of the Deployment that uses an EVS volume to 1 or use other volume types.
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.