Bug 1459678
| Summary: | Unable to mount after client upgrade from 3.9 to 3.10 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | David E. Smith <desmith> | ||||||
| Component: | fuse | Assignee: | bugs <bugs> | ||||||
| Status: | CLOSED EOL | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.10 | CC: | bugs | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-06-20 18:26:56 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1285874 [details]
client logs for failed mount with 3.10 client
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |
Created attachment 1285873 [details] 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