diff --git a/README.md b/README.md index 244d42f99..7e9d092d6 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ The project is currently alpha. While no breaking API changes are currently plan * [Releases](#releases) * [Troubleshooting](#troubleshooting) * [Helm Error: no available release name found](#helm-error-no-available-release-name-found) - + * [NFS volume mount failure: wrong fs type](#nfs-volume-mount-failure-wrong-fs-type) ## Overview [Pravega](http://pravega.io) is an open source distributed storage service implementing Streams. It offers Stream as the main primitive for the foundation of reliable storage systems: *a high-performance, durable, elastic, and unlimited append-only byte stream with strict ordering and consistency*. @@ -501,3 +501,27 @@ kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admi kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' ``` The above commands should resolve the errors and `helm install` should work correctly. + +### NFS volume mount failure: wrong fs type + +If you experience `wrong fs type` issues when pods are trying to mount NFS volumes like in the `kubectl describe po/pravega-segmentstore-0` snippet below, make sure that all Kubernetes node have the `nfs-common` system package installed. You can just try to run the `mount.nfs` command to make sure NFS support is installed in your system. + +In PKS, make sure to use [`v1.2.3`](https://docs.pivotal.io/runtimes/pks/1-2/release-notes.html#v1.2.3) or newer. Older versions of PKS won't have NFS support installed in Kubernetes nodes. + +``` +Events: + Type Reason Age From Message + ---- ------ ---- ---- ------- + Warning FailedMount 10m (x222 over 10h) kubelet, 53931b0d-18f4-49fd-a105-49b1fea3f468 Unable to mount volumes for pod "nautilus-segmentstore-0_nautilus-pravega(79167f33-f73b-11e8-936a-005056aeca39)": timeout expired waiting for volumes to attach or mount for pod "nautilus-pravega"/"nautilus-segmentstore-0". list of unmounted volumes=[tier2]. list of unattached volumes=[cache tier2 pravega-segment-store-token-fvxql] + Warning FailedMount (x343 over 10h) kubelet, 53931b0d-18f4-49fd-a105-49b1fea3f468 (combined from similar events): MountVolume.SetUp failed for volume "pvc-6fa77d63-f73b-11e8-936a-005056aeca39" : mount failed: exit status 32 +Mounting command: systemd-run +Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/79167f33-f73b-11e8-936a-005056aeca39/volumes/kubernetes.io~nfs/pvc-6fa77d63-f73b-11e8-936a-005056aeca39 --scope -- mount -t nfs -o vers=4.1 10.100.200.247:/export/pvc-6fa77d63-f73b-11e8-936a-005056aeca39 /var/lib/kubelet/pods/79167f33-f73b-11e8-936a-005056aeca39/volumes/kubernetes.io~nfs/pvc-6fa77d63-f73b-11e8-936a-005056aeca39 +Output: Running scope as unit run-rc77b988cdec041f6aa91c8ddd8455587.scope. +mount: wrong fs type, bad option, bad superblock on 10.100.200.247:/export/pvc-6fa77d63-f73b-11e8-936a-005056aeca39, + missing codepage or helper program, or other error + (for several filesystems (e.g. nfs, cifs) you might + need a /sbin/mount. helper program) + + In some cases useful info is found in syslog - try + dmesg | tail or so. +```