Description of problem: If a brick's snapshot is missed, and the brick comes up later, the missed snapshot is not recreated. The mount of the missed snap fails. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is a regression bug which is failing with the latest build.
Fix at https://code.engineering.redhat.com/gerrit/26969
Steps to reproduce: 1. Create a 1x3 replica volume 2. Kill a brick on one of the node. 3. Create a snapshot. 4. Bring the brick up using gluster vol start force The missed snapshot should be created and mounted. gluster snap status should show all the snap bricks up and running. df -h should also display the snap brick mounted
Version : glusterfs 3.6.0.18 built on Jun 16 2014 ======= Repeated steps as mentioned in Comment 5 , the missed snapshot is created and mounted, df -h lists it and gluster snapshot status shows all snap bricks are up and running. df -h |grep /var/run/gluster/snaps/d9060b93807741e98f1676d1839e08af 100G 33M 100G 1% /var/run/gluster/snaps/d9060b93807741e98f1676d1839e08af/brick1 gluster snapshot list snap1 snap_1 gluster snapshot status snap_1 Snap Name : snap_1 Snap UUID : c6a53a2b-ed16-46f4-9972-c6d0104fea3d Brick Path : snapshot13.lab.eng.blr.redhat.com:/var/run/gluster/snaps/d9060b93807741e98f1676d1839e08af/brick1/b7 Volume Group : VolGroup1 Brick Running : Yes Brick PID : 18837 Data Percentage : 0.07 LV Size : 100.00g Brick Path : snapshot14.lab.eng.blr.redhat.com:/var/run/gluster/snaps/d9060b93807741e98f1676d1839e08af/brick2/b7 Volume Group : VolGroup1 Brick Running : Yes Brick PID : 6435 Data Percentage : 0.07 LV Size : 100.00g Brick Path : snapshot15.lab.eng.blr.redhat.com:/var/run/gluster/snaps/d9060b93807741e98f1676d1839e08af/brick3/b7 Volume Group : VolGroup1 Brick Running : Yes Brick PID : 25451 Data Percentage : 0.07 LV Size : 100.00g
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. http://rhn.redhat.com/errata/RHEA-2014-1278.html