Bug 1343519 - [Bitrot]: Volume start force restarts the scrubber process, in turn resetting its status
Summary: [Bitrot]: Volume start force restarts the scrubber process, in turn resetting...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: bitrot
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: RajeshReddy
Depends On:
TreeView+ depends on / blocked
Reported: 2016-06-07 12:10 UTC by Sweta Anandpara
Modified: 2018-04-16 17:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-16 17:48:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Sweta Anandpara 2016-06-07 12:10:28 UTC
Description of problem:
glusterd is expected to restart only those processes/translators which are not running. It is expected to leave the rest untouched. 'gluster volume <volname> start force' (which is also the documented workaround for BZ 1341934) in turn ends up restarting the scrub process in every node, resetting the statistics that it would have collected until then. 

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

How reproducible:

Steps to Reproduce:
1. Have a volume with bitrot enabled and note down the scrub pid
2. Execute a gluster volume start force and again note down the scrub pid

Actual results:
The pid changes after volume start force is executed. 'gluster volume bitrot scrub status' is reset to 0.

Expected results:
Scrub process, if it is running, should not be impacted by volume start force. This in turn would leave the scrub status as how it was before.

Note You need to log in before you can comment on or make changes to this bug.