CephFS: mount failed: mount failed: exit status 1

2/14/2020

Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 --scope -- mount -t ceph -o name=kubernetes-dynamic-user-41748797-4ea2-11ea-b682-defbd1d056a0,secret=AQA5tkVedrrdORAAWtrhAYBMNJBXsDqgSgWv0g== ceph-mon.ceph.svc.cluster.local:6789:/volumes/kubernetes/kubernetes/kubernetes-dynamic-pvc-4174871a-4ea2-11ea-b682-defbd1d056a0 /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 Output: Running scope as unit: run-r4a7962524413479a861d0cdc02f9592b.scope couldn't finalize options: -34 Warning FailedMount 9m35s kubelet, minikube MountVolume.SetUp failed for volume "pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8" : CephFS: mount failed: mount failed: exit status 1 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 --scope -- mount -t ceph -o name=kubernetes-dynamic-user-41748797-4ea2-11ea-b682-defbd1d056a0,secret=AQA5tkVedrrdORAAWtrhAYBMNJBXsDqgSgWv0g== ceph-mon.ceph.svc.cluster.local:6789:/volumes/kubernetes/kubernetes/kubernetes-dynamic-pvc-4174871a-4ea2-11ea-b682-defbd1d056a0 /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 Output: Running scope as unit: run-r15199da4f3c242acbbff2c1e8b627bed.scope couldn't finalize options: -34 Warning FailedMount 9m3s kubelet, minikube MountVolume.SetUp failed for volume "pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8" : CephFS: mount failed: mount failed: exit status 1 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 --scope -- mount -t ceph -o name=kubernetes-dynamic-user-41748797-4ea2-11ea-b682-defbd1d056a0,secret=AQA5tkVedrrdORAAWtrhAYBMNJBXsDqgSgWv0g== ceph-mon.ceph.svc.cluster.local:6789:/volumes/kubernetes/kubernetes/kubernetes-dynamic-pvc-4174871a-4ea2-11ea-b682-defbd1d056a0 /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 Output: Running scope as unit: run-rd0eba6d627054dbe9ca488f05bb603cf.scope couldn't finalize options: -34 Warning FailedMount 5m48s (x2 over 8m4s) kubelet, minikube Unable to attach or mount volumes: unmounted volumes=[pvc], unattached volumes=[pvc default-token-rc9k2 ceph-cm-test]: timed out waiting for the condition Warning FailedMount 112s (x5 over 7m59s) kubelet, minikube (combined from similar events): MountVolume.SetUp failed for volume "pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8" : CephFS: mount failed: mount failed: exit status 1 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 --scope -- mount -t ceph -o name=kubernetes-dynamic-user-41748797-4ea2-11ea-b682-defbd1d056a0,secret=AQA5tkVedrrdORAAWtrhAYBMNJBXsDqgSgWv0g== ceph-mon.ceph.svc.cluster.local:6789:/volumes/kubernetes/kubernetes/kubernetes-dynamic-pvc-4174871a-4ea2-11ea-b682-defbd1d056a0 /var/lib/kubelet/pods/3a4bc496-b994-49d2-96f4-bfd966824674/volumes/kubernetes.io~cephfs/pvc-947a7e07-b8fa-48d1-ae11-89ac949ac3a8 Output: Running scope as unit: run-r56f5716008b14ca19520fc6b9ebb3493.scope couldn't finalize options: -34

-- chinasubbareddy
cephfs
kubernetes

1 Answer

2/15/2020

Had you run a search for that couldn't finalize options: -34 error, you would have discovered the existing Ceph bug and the mailing list thread discussing it where they say that the name= is too long. You should try to shorten the name, maybe by removing kubernetes-dynamic- from the name.

Since you didn't include any version information in your question, no one can say whether the recent release of 14.2.7 will help you or not, but it contains security updates so if you're not running 14.2.7 already, you are strongly encouraged to upgrade anyway.

-- mdaniel
Source: StackOverflow