Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume is not able to mount/attach in case of "xfs" file system due to duplicate UUID #56

Closed
w3aman opened this issue Mar 10, 2020 · 0 comments · Fixed by #63
Closed
Assignees
Milestone

Comments

@w3aman
Copy link
Contributor

w3aman commented Mar 10, 2020

what happened:
i provisioned volume with fstype as "xfs" in storageclass. Application was succesfully deployed. When i tried to clone the volume, pvc gets bound but application stuck in container creating state.
Giving error as below:

  Type     Reason                  Age                   From                     Message
  Warning  FailedScheduling        <unknown>             default-scheduler        Failed to bind volumes: pv "pvc-aeadf930-2f7f-4e66-94d3-bd4366e0550b" node affinity doesn't match node "e2e1-node3": No matching NodeSelectorTerms
  Normal   Scheduled               <unknown>             default-scheduler        Successfully assigned aman/percona1-7c776f8558-l2vxk to e2e1-node1
  Warning  FailedScheduling        <unknown>             default-scheduler        AssumePod failed: pod 300233c3-1de6-42a4-87d2-82bba6c284a3 is in the cache, so can't be assumed
  Normal   SuccessfulAttachVolume  5m17s                 attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-aeadf930-2f7f-4e66-94d3-bd4366e0550b"
  Warning  FailedMount             3m14s                 kubelet, e2e1-node1      Unable to attach or mount volumes: unmounted volumes=[data-vol], unattached volumes=[data-vol default-token-tjqfq]: timed out waiting for the condition
  Warning  FailedMount             62s (x10 over 5m13s)  kubelet, e2e1-node1      MountVolume.SetUp failed for volume "pvc-aeadf930-2f7f-4e66-94d3-bd4366e0550b" : kubernetes.io/csi: mounter.SetupAt failed: rpc error: code = Internal desc = rpc error: code = Internal desc = not able to format and mount the zvol
  Warning  FailedMount             58s                   kubelet, e2e1-node1      Unable to attach or mount volumes: unmounted volumes=[data-vol], unattached volumes=[default-token-tjqfq data-vol]: timed out waiting for the condition

Storage class yaml is used as below:

kind: StorageClass
metadata:
  name: zfs-sc
allowVolumeExpansion: true
parameters:
  volblocksize: "4k"
  compression: "off"
  dedup: "off"
  fstype: "xfs"
  poolname: "test-pool"
provisioner: zfs.csi.openebs.io
volumeBindingMode: WaitForFirstConsumer

Because of duplicate UUID volume mount is getting failed in case xfs file system.
To avoid this mountOption as nouuid can be used, something like this as it worked for me:

kind: StorageClass
metadata:
  name: openebs-zfspv1
allowVolumeExpansion: true
parameters:
  fstype: "xfs"
  poolname: "zfspv-pool"
provisioner: zfs.csi.openebs.io
volumeBindingMode: WaitForFirstConsumer
mountOptions:
  - nouuid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants