Description of problem: Creating a snapshot doesn't inherit the snap-max-hard-limit of the volume and always shows as 256. Version-Release number of selected component (if applicable): glusterfs-3.7.5-0.3 How reproducible: Always Steps to Reproduce: 1.Create and start a volume. 2.Set the snap-max-hard-limit for the volume as 100 Volume : testvolume snap-max-hard-limit : 100 Effective snap-max-hard-limit : 100 Effective snap-max-soft-limit : 20 (20%) 3.Create a snapshot of the volume and observe that in info file under /var/lib/glusterd/snaps/snap-name/snap-id/info, the snap-max-hard-limit is shown as 256. 4.Because of this the clone which is created out of this snapshot gets the snap-max-hard-limit as 256 as well. Actual results: Creating a snapshot doesn't inherit the snap-max-hard-limit of the volume and always shows as 256. Expected results: Snapshot info file should show the same snp-max-hard-limit as set for the volume. Additional info:
Fix sent for master (upstream). http://review.gluster.org/#/c/12437/
Master URL: http://review.gluster.org/#/c/12437/ Release 3.7 URL : http://review.gluster.org/#/c/12492/ RHGS 3.1.2 URL : https://code.engineering.redhat.com/gerrit/#/c/60677/
Verified this bug with glusterfs-3.7.5-7 and its working as expected. If we set the snap-max-hard-limit of the volume to some value say 20 Volume : testvolume snap-max-hard-limit : 20 Effective snap-max-hard-limit : 20 Effective snap-max-soft-limit : 18 (90%) and create a snapshot of this volume, the info file under /var/lib/glusterd/snaps/snap-name/snap-id/ shows the correct value of snap-max-hard-limit and it takes the value from its corresponding volume. Similarly, if we create a clone from this snapshot, the cloned volume takes the snap-max-hard-limit's value from the snapshot's value and can be seen proper in the info file under /var/lib/glusterd/vols/clone-name. Since this is working as expected, marking this bug as 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://rhn.redhat.com/errata/RHBA-2016-0193.html