Bug 1275616

Summary:	snap-max-hard-limit for snapshots always shows as 256 in info file.
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	asengupt, bugs, rjoseph, sraj, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	SNAPSHOT
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1275525
Clones:	1277390 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:41:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1275525
Bug Blocks:	1277390

Comment 1 Vijay Bellur 2015-10-28 09:08:27 UTC

REVIEW: http://review.gluster.org/12437 (snapshot: Inherit snap-max-hard-limit from original volume) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2015-11-03 06:38:10 UTC

COMMIT: http://review.gluster.org/12437 committed in master by Rajesh Joseph (rjoseph) 
------
commit 1f74a3efbd0337759878ffff5cd4ee6782ddfe3f
Author: Avra Sengupta <asengupt>
Date:   Wed Oct 28 12:30:34 2015 +0530

    snapshot: Inherit snap-max-hard-limit from original volume
    
    A snapshot should inherit snap-max-hard-limit from the original
    volume while being created and when being restored to, it should
    restore the same.
    
    Similarly a clone taken from a snapshot should inherit
    snap-max-hard-limit from the snapshot.
    
    Change-Id: If8e90e2ffc10e22086b803ac8e2638a16bcec968
    BUG: 1275616
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/12437
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: mohammed rafi  kc <rkavunga>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Niels de Vos 2016-06-16 13:41:27 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user