Description of problem: ======================= Following are the few things in the "man gluster" for snapshot needs to be changed/add. 1) Needs to add snapshot help under "snapshot commands tree" - + snapshot help Display help for the snapshot command. 2) Needs to add following text for "snapshot info [snapname | (volume <volname>)]" - + If snapname is specified then info of the mentioned snapshot is displayed. If volname is specified then info of all snap-shots belonging to that volume is displayed. If both snapname and volname is not specified then info of all the snapshots present in the system are displayed. 3) Need to add text for "snap-max-hard-limit" under "snapshot config" 4) Need to change the below text - Upon reaching the hard-limit, further snapshot creations will not be allowed. + Upon reaching the effective-hard-limit, further snapshot creations will not be allowed. Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.6.0.27-1.el6rhs.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. man gluster
upstream patch : http://review.gluster.org/#/c/9976/
Version : glusterfs-3.7.1-1.el6rhs.x86_64 Some changes are not updated in man gluster --> snapshot config section: snap-max-hard-limit, snap-max-soft-limit and auto-delete are global options, that will be inherited by all volumes in the system and cannot be set to individual volumes . Here snap-max-hard-limit should be removed as it can be set to individual volumes and to the system and a separate section on snap-max-hard-limit should be added as mentioned in the 'Description' --> Also 4th point mentioned in Description is not updated 4) Need to change the below text - Upon reaching the hard-limit, further snapshot creations will not be allowed. + Upon reaching the effective-hard-limit, further snapshot creations will not be allowed. --> The system limit takes precedence over the volume specific limit --> This statement is not true in all cases. Which ever limit is the lowest takes priority.
Mainline - http://review.gluster.org/#/c/11229/ 3.7 - http://review.gluster.org/#/c/11292/ Downstream - https://code.engineering.redhat.com/gerrit/51016
Version :glusterfs-3.7.1-4.el6rhs.x86_64 Changes are updates in man gluster : snap-max-soft-limit and auto-delete are global options, that will be inherited by all volumes in the system and cannot be set to individual volumes. When auto-delete feature is disabled, then upon reaching the "Effective snap-max-hard-limit", further snapshot creations will not be allowed. snap-max-hard-limit can be set globally, as well as per volume. The lowest limit between the global system limit and the volume specific limit, becomes the "Effective snap-max-hard-limit" for a volume. Marking the bug '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/RHSA-2015-1495.html