Description of problem: Unable to mount glusterfs volume on client with usrquota option Version-Release number of selected component (if applicable): glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64 glusterfs-3.4.0.57rhs-1.el6_5.x86_64 glusterfs-fuse-3.4.0.57rhs-1.el6_5.x86_64 How reproducible: Everytime Steps to Reproduce: 1. add usrquota to options list 2. attempt to mount 3. fails Actual results: /usr/bin/fusermount-glusterfs: mount failed: Invalid argument Mount failed. Please check the log file for more details. [2014-01-29 00:58:47.071057] I [client-handshake.c:1492:client_setvolume_cbk] 0-osgears-client-0: Server and Client lk-version numbers are not same, reopening the fds [2014-01-29 00:58:47.075188] I [fuse-bridge.c:5874:fuse_graph_setup] 0-fuse: switched to graph 0 [2014-01-29 00:58:47.075757] I [client-handshake.c:450:client_set_lk_version_cbk] 0-osgears-client-0: Server lk version = 1 [2014-01-29 00:58:47.076447] I [fuse-bridge.c:5715:fuse_thread_proc] 0-fuse: unmounting /var/lib/openshift [2014-01-29 00:58:47.076872] W [glusterfsd.c:1099:cleanup_and_exit] (-->/lib64/libc.so.6(clone+0x6d) [0x7fa707b6eb6d] (-->/lib64/libpthread.so.0(+0x79d1) [0x7fa7082019d1] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xcd) [0x4052ad]))) 0-: received signum (15), shutting down [2014-01-29 00:58:47.076920] I [fuse-bridge.c:6412:fini] 0-fuse: Unmounting '/var/lib/openshift'. Expected results: Mount with usrquota option Additional info: usrquota on lv/mount is required for Openshift. Attempting to use gluster to serve /var/lib/openshift for gears and for the ability to quickly recover from node failures.
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.