Created attachment 1337263 [details] mount log file Description of problem: Mounting an activated snapshot to a client by giving the command "mount -t glusterfs 10.70.42.243:/snaps/test0/bravo /mnt/test0/" fails. Here, test0 is the snapshot name and bravo is the volume name Info of the volume: [root@dhcp42-243 ~]# gluster v info Volume Name: bravo Type: Distributed-Replicate Volume ID: 575514e1-fd58-4205-a418-d551a3463280 Status: Started Snapshot Count: 254 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.70.42.243:/bricks/brick0/bravo Brick2: 10.70.42.206:/bricks/brick0/bravo Brick3: 10.70.43.53:/bricks/brick0/bravo Brick4: 10.70.43.152:/bricks/brick0/bravo Brick5: 10.70.43.141:/bricks/brick0/bravo Brick6: 10.70.42.9:/bricks/brick0/bravo Options Reconfigured: nfs.disable: on transport.address-family: inet features.barrier: disable features.uss: enable changelog.changelog: on cluster.enable-shared-storage: enable auto-delete: enable Output of the mount command: [root@dhcp43-240 ~]# mount -t glusterfs 10.70.42.243:/snaps/test0/bravo /mnt/test0/ Mount failed. Please check the log file for more details. Version-Release number of selected component (if applicable): [root@dhcp42-243 ~]# rpm -qa | grep gluster glusterfs-3.8.4-48.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-48.el7rhgs.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.3.x86_64 glusterfs-debuginfo-3.8.4-48.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-48.el7rhgs.x86_64 glusterfs-fuse-3.8.4-48.el7rhgs.x86_64 glusterfs-rdma-3.8.4-48.el7rhgs.x86_64 python-gluster-3.8.4-48.el7rhgs.noarch glusterfs-libs-3.8.4-48.el7rhgs.x86_64 glusterfs-api-3.8.4-48.el7rhgs.x86_64 glusterfs-server-3.8.4-48.el7rhgs.x86_64 vdsm-gluster-4.17.33-1.2.el7rhgs.noarch glusterfs-cli-3.8.4-48.el7rhgs.x86_64 gluster-nagios-addons-0.2.9-1.el7rhgs.x86_64 [root@dhcp42-243 ~]# How reproducible: 2/2 Steps to Reproduce: 1. Create and start a volume. 2. Mount the volume on a client and do some I/O's at the mount point. 3. Create a snapshot and activate it. 4. Mount the snapshot on client using the command "mount -t glusterfs <node ip>:/snaps/<snapname>/<volname> /mnt/<mountname>" Actual results: Mount fails with output : Mount failed. Please check the log file for more details. Expected results: Should be mounted successfully. Additional info: Output of the log file from the failed mount is attached. Looking at the log file it seems that the issue is related to the subdir mount.
master patch : https://review.gluster.org/#/c/18506/ release-3.12 patch : https://review.gluster.org/#/c/18507
Build no. : 3.8.4-50 Tried the same scenario again on the 3.8.4-50 build but getting the same error message in the log file. Output of the log file : "[2017-10-24 08:37:45.343189] I [MSGID: 100030] [glusterfsd.c:2441:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.8.4 (args: /usr/sbin/glusterfs --volfile-server=10.70.42.243 --volfile-id=snaps --subdir-mount=/snapC1/charlie /mnt/snapC1) [2017-10-24 08:37:45.362971] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-10-24 08:37:45.365993] E [glusterfsd-mgmt.c:1798:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2017-10-24 08:37:45.366039] E [glusterfsd-mgmt.c:1934:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:snaps) [2017-10-24 08:37:45.366420] W [glusterfsd.c:1300:cleanup_and_exit] (-->/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0x90) [0x7f25485fc840] -->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x680) [0x557eb0014d00] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x557eb000df4b] ) 0-: received signum (0), shutting down [2017-10-24 08:37:45.366478] I [fuse-bridge.c:5833:fini] 0-fuse: Unmounting '/mnt/snapC1'. [2017-10-24 08:37:45.371443] I [fuse-bridge.c:5838:fini] 0-fuse: Closing fuse connection to '/mnt/snapC1'. " Volume info : [root@dhcp42-243 ~]# gluster v info Volume Name: charlie Type: Distributed-Replicate Volume ID: db9a7a7c-5bff-4eff-b363-0d4790f68923 Status: Started Snapshot Count: 1 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.70.42.243:/bricks/brick0/charlie Brick2: 10.70.42.206:/bricks/brick0/charlie Brick3: 10.70.43.53:/bricks/brick0/charlie Brick4: 10.70.43.152:/bricks/brick0/charlie Brick5: 10.70.43.141:/bricks/brick0/charlie Brick6: 10.70.42.9:/bricks/brick0/charlie Options Reconfigured: features.uss: enable features.barrier: disable transport.address-family: inet nfs.disable: on cluster.enable-shared-storage: disable auto-delete: enable [root@dhcp42-243 ~]# Hence moving to FAILED_QA.
I Tried with version 3.8.4-50, and I was able to mount the snapshot with command mount -t glusterfs <hostname>:/snaps/<snapname>/volname <mount point> Can you please cross check it.
Build no. : 3.8.4-50 Followed the steps in description. Snapshot mount is now possible. Hence, moving to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3276