Bug 809847

Summary:	volume set cluster.background-self-heal-count can accept invalid values.
Product:	[Community] GlusterFS	Reporter:	Kaushal <kaushal>
Component:	core	Assignee:	Kaushal <kaushal>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:26:25 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:

Description Kaushal 2012-04-04 13:59:58 UTC

cluster.background-self-heal-count can accept negative numbers even though min has been specified as 0.

For eg:
#gluster volume set test cluster.background-self-heal-count -9000
Set volume successful

#gluster volume info test

Volume Name: test
Type: Replicate
Volume ID: 1db29f5f-08c6-48d2-b3d4-7bd93c14d810
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: arch:/export/1
Brick2: arch:/export/2
Options Reconfigured:
cluster.background-self-heal-count: -9000

Comment 1 Kaushal 2012-07-11 05:27:31 UTC

Patch 81e7464a54165b5d8b40847355d3bb6fe7b6e9df (libglusterfs : Fix validation for integer volume options) in master (review @ http://review.gluster.com/3084) fixes this.