Oh I'm sorry, I totally misread that - didn't realise it was on the client. Clarification for below logs: - 'dev_static' is the gluster volume. - 'int-kube-01' is the gluster client. - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting '10.51.70.151:/dev_static/iss3dev-static', where 'iss3dev-static' is a directory inside the gluster mount 'dev_static'. - FYI only, we are essentially mounting directories inside gluster volumes as per Kubernetes example: https://github.com/kubernetes/examples/blob/master/staging/volumes/glusterfs/README.md root@int-kube-01:/var/log/glusterfs # tail -20 mnt.log [2017-11-07 21:15:03.561470] I [MSGID: 100030] [glusterfsd.c:2524:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.12.2 (args: /usr/sbin/glusterfs --volfile-server=10.51.70.151 --volfile-id=/dev_static /mnt) [2017-11-07 21:15:03.571205] W [MSGID: 101002] [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is deprecated, preferred is 'transport.address-family', continuing with correction [2017-11-07 21:15:03.584098] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 No new log entries appear after executing the following to demonstrate the problem: root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static # touch test root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static # mkdir testdir2 root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static # ls -ltar total 0 -rw-r--r--. 1 root root 0 Nov 6 10:10 test root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static # cd testdir2 root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static/testdir2 # ls -la total 0 root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static/testdir2 # cd .. root@int-kube-01:/var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static# ls -ltar total 0 -rw-r--r--. 1 root root 0 Nov 6 10:10 test The mount entry looks like: root@int-kube-01:~ # mount | grep iss3dev-static 10.51.70.151:/dev_static on /var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
