Why can't my app access or write to PVCs?
Virtual Private Cloud Classic infrastructure
When you mount a PVC to your pod, you might experience errors when accessing or writing to the PVC.
- List the pods in your cluster and review the status of the pod.
kubectl get pods - Find the root cause for why your app can't access or write to the PVC.
kubectl describe pod <pod_name>kubectl logs <pod_name> - Review common errors that can occur when you mount a PVC to a pod.
| Symptom or error message | Description | Steps to resolve |
|---|---|---|
Your pod is stuck in a ContainerCreating or CrashLoopBackOff state. MountVolume.SetUp failed for volume ... read-only. |
The IBM Cloud infrastructure back end experienced network problems. To protect your data and to avoid data corruption, IBM Cloud automatically disconnected the block storage server to prevent write operations on block storage instances. | See Block storage: Block storage changes to read-only |
failed to mount the volume as "ext4", it already contains xfs. Mount error: mount failed: exit status 32. |
You want to mount an existing block storage instance that was set up with an XFS file system. When you created the PV and the matching PVC, you specified an ext4 or no file system. The file system that you specify
in your PV must be the same file system that is set up in your block storage instance. |
See Block storage: Mounting existing block storage to a pod fails due to the wrong file system |