Bug 1238634
Summary: | Though scrubber settings changed on one volume log shows all volumes scrubber information | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RajeshReddy <rmekala> | |
Component: | bitrot | Assignee: | Kotresh HR <khiremat> | |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.1 | CC: | annair, asrivast, bmohanra, byarlaga, knarra, mzywusko, rhs-bugs, sankarshan, smohan, storage-qa-internal, vshankar | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.2 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.5-3 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when bitrot was configured on multiple volumes in a cluster and the scrubber-frequency was changed for one volume, the frequency for all other volumes w.r.t to its scrubber-frequency was reset. This is fixed to change scrubber-frequency only to corresponding volume and log it accordingly.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1252825 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-01 05:28:13 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: | ||||
Bug Blocks: | 1252825, 1256669, 1260783 |
Description
RajeshReddy
2015-07-02 10:30:18 UTC
Upstream patches are merged. Upstream Patch (master): http://review.gluster.org/11897 Upstream Patch (3.7): http://review.gluster.org/12010 Patch had merged before branching of rhgs-3.1.2 and hence already in downstream code. Moving to ON_QA Verified and works fine with build glusterfs-3.7.5-0.3.el6rhs.x86_64. When scrubber frequency is changed on a volume, scrub.log has entries just for the volume on which the scrubber frequency has changed and not for all the volumes in the cluster. Changing scrubber frequency on one volume does not reset the scrubber options on all the other volumes. Marking this 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 |