Bug 1228135
Summary: | [Bitrot] Gluster v set <volname> bitrot enable command succeeds , which is not supported to enable bitrot | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anil Shah <ashah> | |
Component: | bitrot | Assignee: | Gaurav Kumar Garg <ggarg> | |
Status: | CLOSED ERRATA | QA Contact: | RajeshReddy <rmekala> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.1 | CC: | annair, asriram, asrivast, divya, ggarg, mzywusko, nsathyan, rhs-bugs, smohan, storage-qa-internal, vagarwal, vshankar | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.1 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.1-13 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, all bitrot commands that use the "gluster volume set <volname> *" command to start or stop bitd and scrub daemon that set any value for bitrot and crubber daemon succeeded. But gluster did not support "gluster volume set <volname> *" command to reconfigure the BitRot options. Due to this, when the gluster volume set <volname> command is executed, then the bitrot and scrub daemon crashed. With this fix, gluster accepts only “gluster volume bitrot <VOLNAME> *” commands for bitrot and scrub operations.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1229134 (view as bug list) | Environment: | ||
Last Closed: | 2015-10-05 07:10:26 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: | 1216951, 1223636, 1229134, 1232589, 1251815 |
Description
Anil Shah
2015-06-04 09:47:34 UTC
Doc text is edited. Please sign off to be included in Known Issues. hi, this doc text looks good to me. upstream patch for this bug is already merged will backport it. http://review.gluster.org/#/c/11118/ downstream patch available for this bug: https://code.engineering.redhat.com/gerrit/#/c/55756/ Tested with build "" and with gluster vol set command is not allowing to change bitrot configuration [root@rhs-client9 data]# gluster vol set dht4 bitrot enable volume set: failed: 'gluster volume set <VOLNAME> bitrot' is invalid command. Use 'gluster volume bitrot <VOLNAME> {enable|disable}' instead. [root@rhs-client9 data]# gluster vol set dht4 [2015-08-27 07:53:58.738372] A [MSGID: 118023] [bit-rot-scrub.c:228:bitd_compare_ckum] 0-dht4-bit-rot-0: Object checksum mismatch: /data/bitrot1 [GFID: 9f472773-c993-41d7-b5c3-1a206c36fc7c | Brick: /rhs/brick1/dht4] -bash: Brick:: command not found Usage: volume set <VOLNAME> <KEY> <VALUE> [root@rhs-client9 data]# [2015-08-27 07:53:58.738670] A [MSGID: 118024] [bit-rot-scrub.c:248:bitd_compare_ckum] 0-dht4-bit-rot-0: Marking /data/bitrot1 [GFID: 9f472773-c993-41d7-b5c3-1a206c36fc7c | Brick: /rhs/brick1/dht4] as corrupted.. -bash: Brick:: command not found -bash: [2015-08-27: command not found [root@rhs-client9 data]# gluster vol set Usage: volume set <VOLNAME> <KEY> <VALUE> [root@rhs-client9 data]# gluster vol set dht scrub-frequency daily volume set: failed: 'gluster volume set <VOLNAME> scrub-frequency' is invalid command. Use 'gluster volume bitrot <VOLNAME> scrub-frequency {hourly|daily|weekly|biweekly|monthly}' instead. [root@rhs-client9 data]# gluster vol set dht scrub pause volume set: failed: 'gluster volume set <VOLNAME> scrub' is invalid command. Use 'gluster volume bitrot <VOLNAME> scrub {pause|resume}' instead. [root@rhs-client9 data]# gluster vol set dht scrub-throttle pause volume set: failed: 'gluster volume set <VOLNAME> scrub-throttle' is invalid command. Use 'gluster volume bitrot <VOLNAME> scrub {pause|resume}' instead. [root@rhs-client9 data]# gluster vol set dht4 scrub-throttle normal volume set: failed: 'gluster volume set <VOLNAME> scrub-throttle' is invalid command. Use 'gluster volume bitrot <VOLNAME> scrub {pause|resume}' instead. 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-1845.html |