Description of problem: Not able to mount gluster volume on client host. Version-Release number of selected component (if applicable): Server : glusterfs 3.4.2 Client : glusterfs 3.3.1 Actual results: unknown option _netdev (ignored) Mount failed. Please check the log file for more details. Expected results: gluster volume should mount in client hosts Additional info: Not able to mount arm server gluster volume on client hosts and seeing below error message. Same configuration is working fine when I mount inter servers gluster volume. root@client:~# mount /mnt/glusterfs unknown option _netdev (ignored) Mount failed. Please check the log file for more details. root@client:~# tail -5 /var/log/glusterfs/mnt-glusterfs.log [2014-02-06 17:20:25.790753] I [glusterfsd.c:1666:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.1 [2014-02-06 17:20:25.794425] E [glusterfsd-mgmt.c:1559:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2014-02-06 17:20:25.794457] E [glusterfsd-mgmt.c:1627:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:/gluster-vol) [2014-02-06 17:20:25.794629] W [glusterfsd.c:831:cleanup_and_exit] (-->/usr/lib/libgfrpc.so.0(rpc_clnt_notify+0xa5) [0x7f78ec452565] (-->/usr/lib/libgfrpc.so.0(rpc_clnt_handle_reply+0xa5) [0x7f78ec451b65] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x304) [0x7f78ecb04804]))) 0-: received signum (0), shutting down [2014-02-06 17:20:25.794652] I [fuse-bridge.c:4648:fini] 0-fuse: Unmounting '/mnt/glusterfs'.
Not able to mount arm server gluster volume on client hosts and seeing below error message. Same configuration is working fine when I mount inter servers gluster volume.
From comment0, this is the issue with glusterfs-3.4.2 and its a glusterfs bug ( wrt ARM Arch ) Changing the product accordingly FYI - Red Hat Storage is the downstream of glusterfs Changing the product/component accordingly
Any specific reason you are using "Client : glusterfs 3.3.1" older client version than server's. I think you can try updating the clients bits as per server. Also the mount command should be "mount -t glusterfs <Gluster Node IP>:/<olname> <mount point>" for native mounts
This might help you https://lists.nongnu.org/archive/html/gluster-devel/2014-01/msg00175.html
Thanks a lot SATHEESARAN and Lalatendu for you info. @SATHEESARAN even I am thing the same and planning to down grade to Version 3.3.1 on arm server nodes because same configuration is working fine when I mount intel gluster volume. Could you please help me on downgrading glsuter vestion to 3.3.1? As I installed gluster server on arm hosts using source code I cant remove it using apt-get or dpkg -r.I don't find any gluster un-installation instructions for source code.
Issue resolved after downgraded Gluster version to 3.3.2 on server and am able to mount gluster volume on client hosts now. Is Gluster version 3.3.2 stable version ?
Venkatesh, Yes 3.3.2 is a stable version. But I would suggest to move to a more recent version e.g. 3.4.2. Because I think 3.4 will be maintained for longer more than 3.3 branch and there are some performance improvements in 3.4.
Lalatendu, How can you say its not a bug? because when a install latest version 3.4.2 on my arm based servers not able to mount gluster volume on client hosts and same configuration working fine for Intel arch. As SATHEESARAN also mentioned above this is the issue with glusterfs-3.4.2 and its a glusterfs bug ( wrt ARM Arch ). Is Redhat trying to fix the bug? could you someone please provide more details on this bug solution?
Venkatesh, May be I didn't understand your issue correctly. Are you saying that with 3.4.2 (wrt ARM Arch) , if servers and clients have the version 3.4.2, clients are not able to mount gluster volume? if yes it is definitely a bug. If you are looking for the compatibility of 3.3.2 clients with 3.4.2 servers I am not sure. We will have to talk somebody in community about it. I am just working as part of community (GlusterFS) to fix the bug. Red Hat is not involved with this bug.
Issue resolved after downgrading gluster version to 3.3.2.
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life.\ \ If this bug still exists in a later release please reopen this and change the version or open a new bug.