Bug 1252825

Summary:	Though scrubber settings changed on one volume log shows all volumes scrubber information
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	bitrot	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:	bugs <bugs>
Priority:	unspecified
Version:	mainline	CC:	annair, asrivast, bugs, nsathyan, rmekala, vshankar
Target Milestone:	---	Keywords:	Reopened, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1238634
Clones:	1256669 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:31:51 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:	1238634
Bug Blocks:	1256669

Description Kotresh HR 2015-08-12 09:58:44 UTC

+++ This bug was initially created as a clone of Bug #1238634 +++

Description of problem:
===================
Though scrubber settings changed on one volume, we are showing all scrubber settings information

Version-Release number of selected component (if applicable):
=================


How reproducible:
=====================



Steps to Reproduce:
==============
1.Create a few volumes and enable bitrot 
2.Change scrub frequency from default to hourly on one of the volume and check the scrubber log
3.

Actual results:
===============
Log shows all volume scrubber information and it is confusing 

Expected results:
=============
It would be good to show only affected volume settings

Comment 1 Anand Avati 2015-08-12 11:53:16 UTC

REVIEW: http://review.gluster.org/11897 (features/bitrot: Fix scrubber frequency set) posted (#1) for review on master by Kotresh HR (khiremat)

Comment 2 Anand Avati 2015-08-12 14:03:11 UTC

REVIEW: http://review.gluster.org/11897 (features/bitrot: Fix scrubber frequency set) posted (#2) for review on master by Kotresh HR (khiremat)

Comment 3 Anand Avati 2015-08-13 06:15:47 UTC

REVIEW: http://review.gluster.org/11897 (features/bitrot: Fix scrubber frequency set) posted (#3) for review on master by Kotresh HR (khiremat)

Comment 4 Anand Avati 2015-08-18 10:10:25 UTC

REVIEW: http://review.gluster.org/11897 (features/bitrot: Fix scrubber frequency set) posted (#4) for review on master by Venky Shankar (vshankar)

Comment 5 Anand Avati 2015-08-21 06:49:15 UTC

REVIEW: http://review.gluster.org/11897 (features/bitrot: Fix scrubber frequency set) posted (#5) for review on master by Kotresh HR (khiremat)

Comment 6 Anand Avati 2015-08-24 04:32:12 UTC

COMMIT: http://review.gluster.org/11897 committed in master by Venky Shankar (vshankar) 
------
commit a586b30c1bd968d23562406cefbb76b82a0e236c
Author: Kotresh HR <khiremat>
Date:   Wed Aug 12 15:25:03 2015 +0530

    features/bitrot: Fix scrubber frequency set
    
    When bitrot is configured on multiple volumes
    in a cluster and scrubber-frequency is changed
    for one volume, it is resetting frequency for
    all other volumes w.r.t to its scrubber-frequency.
    This should not happen. Changing scrubber-frequency
    should affect only that volume on which it is set.
    This patch fixes the issue.
    
    Also restricted the logs to the configure volume.
    
    Change-Id: I90d6e864b131e3d8dd4010079a00f924032f2098
    BUG: 1252825
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/11897
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Reviewed-by: Venky Shankar <vshankar>

Comment 7 Nagaprasad Sathyanarayana 2015-10-25 15:14:12 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 8 Niels de Vos 2016-06-16 13:31:51 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