[Bugs] [Bug 1459678] New: Unable to mount after client upgrade from 3.9 to 3.10

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1459678

            Bug ID: 1459678
           Summary: Unable to mount after client upgrade from 3.9 to 3.10
           Product: GlusterFS
           Version: 3.10
         Component: fuse
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: desmith at wustl.edu
                CC: bugs at gluster.org



Created attachment 1285873
  --> https://bugzilla.redhat.com/attachment.cgi?id=1285873&action=edit
client logs for successfully mounting with 3.9 client

Description of problem:
I have an existing GlusterFS file system, whose servers have been upgraded to
Gluster 3.10.0 (from gluster.org). The clients are currently on 3.9, and all is
well. When I try to upgrade the clients to 3.10, though, the mount process
terminates prematurely and the file system is not mounted.

The cluster's versions are, I believe, set correctly. From one of the servers:

gluster> volume get all cluster.op-version
Option                                  Value
------                                  -----
cluster.op-version                      30900
gluster> volume get all cluster.max-op-version
Option                                  Value
------                                  -----
cluster.max-op-version                  31000


Version-Release number of selected component (if applicable):
Servers: Gluster 3.10 (3.10.0-1 RPMs from upstream)
Working Clients: Gluster 3.9 (3.9.1-1 RPMs from upstream)
Non-working Clients: Gluster 3.10 (3.10.0-1 RPMs from upstream)


Attaching logs of successful and unsuccessful mounts. This is the part that
looks "interesting" to me, less than half a second after the mount command is
started:

[2017-06-07 18:09:27.469408] I [fuse-bridge.c:5089:fuse_thread_proc] 0-fuse:
unmounting /mnt

[2017-06-07 18:09:27.470229] W [glusterfsd.c:1329:cleanup_and_exit]
(-->/lib64/libpthread.so.0(+0x7aa1) [0x7f2f5ff98aa1]
-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xcd) [0x4063fd]
-->/usr/sbin/glusterfs(cleanup_and_exit+0x6a) [0x405efa] ) 0-: received signum
(15), shutting down

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.