+++ This bug was initially created as a clone of Bug #1284789 +++ Description of problem: Snapshot creation fails after attach-tier and glusterd crashes Version-Release number of selected component (if applicable): glusterfs-3.7.5-7 How reproducible: Steps to Reproduce: 1. Create a replica 2 volume 2. Attach a replica 2 tier 3. Take a snapshot Actual results: glusterd crashes Expected results: glusterd should not crash Additional info:
It is a regression caused by one of the recent patches as it was working with with previous builds. Patch sent for master.
This bug is fixed and verified with glusterfs-3.7.5-8 build with below steps: [root@dhcp35-228 ~]# gluster --version glusterfs 3.7.5 built on Dec 1 2015 01:29:42 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. [root@dhcp35-228 ~]# gluster volume list tiervolume [root@dhcp35-228 ~]# gluster snapshot create snap1 tiervolume snapshot create: success: Snap snap1_GMT-2015.12.01-11.47.35 created successfully [root@dhcp35-228 ~]# gluster snapshot create snap2 tiervolume snapshot create: success: Snap snap2_GMT-2015.12.01-11.47.47 created successfully [root@dhcp35-228 ~]# gluster snapshot create snap4 tiervolume snapshot create: success: Snap snap4_GMT-2015.12.01-11.47.57 created successfully [root@dhcp35-228 ~]# gluster snapshot create snap3 tiervolume no-timestamp snapshot create: success: Snap snap3 created successfully [root@dhcp35-228 ~]# gluster snapshot create snap5 tiervolume no-timestamp snapshot create: success: Snap snap5 created successfully [root@dhcp35-228 ~]# gluster snapshot list snap1_GMT-2015.12.01-11.47.35 snap2_GMT-2015.12.01-11.47.47 snap4_GMT-2015.12.01-11.47.57 snap3 snap5 There is no glusterd crash observed during multiple snap creations. Hence moving it to Verified state.
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://rhn.redhat.com/errata/RHBA-2016-0193.html