Troubleshooting the Kubernetes Interfaces for Data Fabric FlexVolume Driver
This section describes how to resolve common problems you might encounter when using the Kubernetes Interfaces for Data Fabric FlexVolume driver.
Shared Memory Lock Causes POSIX Failure
- Problem
-
On an upgrade from a previous version of the volume plug-in, POSIX can fail with the following error in the POSIX log file:
Create/Attach to stats shared memory failed. - Possible Cause
-
A shared-memory segment lock can prevent the mount from becoming available to the requested pod.
- Resolution
-
Follow the steps in Troubleshooting loopbacknfs POSIX Client Upgrades to remove the lock. Then retry the operation.
Unable to Access file system
- Problem
-
Storage is not mounted and no errors are generated in the plugin or provisioner logs.
- Possible Cause
-
The fusermount symlink might be broken.
- Resolution
-
If the symlink points to a location other than
/opt/mapr/k8s/bin/fusermount, unlink it using the following command from the command line on the host:
Then re-create the Kubernetes Pod.unlink /bin/fusermount
Pod Container Stuck in Container Creation State During Installation
- Problem
- During installation, the Pod container can become stuck in the container creation
state on a node, and the
/opt/mapr/k8sdirectory is not created. As a result, the plug-in does not get copied to the node.
- Possible Cause
- Unknown.
- Resolution
- Check the installation logs
for an indication that the installation is not completed or the
/opt/mapr/k8sdirectory is not created. Restart the kubelet service in the node:systemctl restart kubelet