Hi, quick question about snapshot mounting: Were there changes in 3.12 that were not mentioned in the release notes for snapshot mounting? I recently upgraded from 3.10 to 3.12 on CentOS (using centos-release-gluster312). The upgrade worked flawless. The volume works fine too. But mounting a snapshot fails with those two error messages: [2017-11-13 08:46:02.300719] E [glusterfsd-mgmt.c:1796:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2017-11-13 08:46:02.300744] E [glusterfsd-mgmt.c:1932:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:snaps) Up to the mounting everything works as before: # gluster snapshot create test home no-timestamp # gluster snapshot activate test # gluster snapshot info test Snapshot : test Snap UUID : 1c07aed0-32f4-4e6b-b5bc-226578fb78e3 Created : 2017-11-13 08:22:07 Snap Volumes: Snap Volume Name : b19a36dd16dd466985fbb0681539fe71 Origin Volume name : home Snaps taken for home : 1 Snaps available for home : 255 Status : Started # mount -t glusterfs sphere-four:/snaps/test/home /mnt/temp/ Mount failed. Please check the log file for more details. The log shows the following: [2017-11-13 08:46:02.289163] I [MSGID: 100030] [glusterfsd.c:2496:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.12.1 (args: /usr/sbin/glusterfs --volfile-server=sphere-four --volfile-id=snaps --subdir-mount=/test/home /mnt/temp) [2017-11-13 08:46:02.292629] 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-13 08:46:02.298278] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-11-13 08:46:02.300719] E [glusterfsd-mgmt.c:1796:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2017-11-13 08:46:02.300744] E [glusterfsd-mgmt.c:1932:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:snaps) [2017-11-13 08:46:02.300903] W [glusterfsd.c:1347:cleanup_and_exit] (-->/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0x90) [0x7feb51ed9e60] -->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x680) [0x55a5dbb97ef0] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x55a5dbb9118b] ) 0-: received signum (0), shutting down [2017-11-13 08:46:02.300928] I [fuse-bridge.c:5833:fini] 0-fuse: Unmounting '/mnt/temp'. [2017-11-13 08:46:02.308875] I [fuse-bridge.c:5838:fini] 0-fuse: Closing fuse connection to '/mnt/temp'. [2017-11-13 08:46:02.308987] W [glusterfsd.c:1347:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7e25) [0x7feb50f70e25] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x55a5dbb91365] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x55a5dbb9118b] ) 0-: received signum (15), shutting down Google was no help so far. Since the mount worked before the upgrade I'm puzzled. What am I missing? Thanks a lot! Richard
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
