Description of problem: Command "gluster volume set <volname> bitrot enable " succeeds. however gluster volume status command shows bitrot process not online and no pid is assigned. Version-Release number of selected component (if applicable): [root@node1 glusterfs]# rpm -qa | grep glusterfs glusterfs-3.7.0-2.el6rhs.x86_64 glusterfs-cli-3.7.0-2.el6rhs.x86_64 glusterfs-libs-3.7.0-2.el6rhs.x86_64 glusterfs-client-xlators-3.7.0-2.el6rhs.x86_64 glusterfs-api-3.7.0-2.el6rhs.x86_64 glusterfs-server-3.7.0-2.el6rhs.x86_64 glusterfs-fuse-3.7.0-2.el6rhs.x86_64 glusterfs-geo-replication-3.7.0-2.el6rhs.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create 4+2 disperse volume 2. Enable bitrot on volume with command gluster v set <volname> bitrot enable 3. check gluster v info and gluster v status Actual results: [root@node1 glusterfs]# gluster v set ecvol bitrot enable volume set: success =============================================== [root@node1 glusterfs]# gluster v status ecvol Status of volume: ecvol Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.47.143:/rhs/brick1/ec1 49155 0 Y 20497 Brick 10.70.47.145:/rhs/brick1/ec2 49154 0 Y 8958 Brick 10.70.47.150:/rhs/brick1/ec3 49154 0 Y 13867 Brick 10.70.47.151:/rhs/brick1/ec4 49154 0 Y 8033 Brick 10.70.47.143:/rhs/brick4/ec5 49156 0 Y 20514 Brick 10.70.47.145:/rhs/brick4/ec6 49155 0 Y 8975 NFS Server on localhost 2049 0 Y 20534 Quota Daemon on localhost N/A N/A Y 20665 Bitrot Daemon on localhost N/A N/A N N/A Scrubber Daemon on localhost N/A N/A N N/A NFS Server on 10.70.47.150 2049 0 Y 13887 Quota Daemon on 10.70.47.150 N/A N/A Y 13955 Bitrot Daemon on 10.70.47.150 N/A N/A N N/A Scrubber Daemon on 10.70.47.150 N/A N/A N N/A NFS Server on 10.70.47.145 2049 0 Y 8995 Quota Daemon on 10.70.47.145 N/A N/A Y 9072 Bitrot Daemon on 10.70.47.145 N/A N/A N N/A Scrubber Daemon on 10.70.47.145 N/A N/A N N/A NFS Server on 10.70.47.151 2049 0 Y 8052 Quota Daemon on 10.70.47.151 N/A N/A Y 8130 Bitrot Daemon on 10.70.47.151 N/A N/A N N/A Scrubber Daemon on 10.70.47.151 N/A N/A N N/A ======================================================================== [root@node1 glusterfs]# gluster v info ecvol Volume Name: ecvol Type: Disperse Volume ID: 75cae01b-8d42-4621-b2ac-6853ea04e90d Status: Started Number of Bricks: 1 x (4 + 2) = 6 Transport-type: tcp Bricks: Brick1: 10.70.47.143:/rhs/brick1/ec1 Brick2: 10.70.47.145:/rhs/brick1/ec2 Brick3: 10.70.47.150:/rhs/brick1/ec3 Brick4: 10.70.47.151:/rhs/brick1/ec4 Brick5: 10.70.47.143:/rhs/brick4/ec5 Brick6: 10.70.47.145:/rhs/brick4/ec6 Options Reconfigured: features.bitrot: enable features.quota-deem-statfs: on features.inode-quota: on features.quota: on performance.readdir-ahead: on Expected results: Volume set option is not supported to enable bitrot. Additional info:
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