Hide Forgot
Description of problem: vlaues for Number of Scrubbed files, Number of Unsigned files, Last completed scrub time and Duration of last scrub gets reset to default value when glusterd or bitd or one of the node reboots. Version-Release number of selected component (if applicable): glusterfs-3.7.5-12.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Install latest glusterfs build. 2. Now wait for scrubber to scrub some of the files so that scrub status gives the output. 3. Now either restart glusterd / bitd / one of the nodes in the cluster. Actual results: I see that all the values for Number of Scrubbed files, Number of Unsigned files, Last completed scrub time and Duration of last scrub gets reset to default Expected results: All the values for Number of Scrubbed files, Number of Unsigned files, Last completed scrub time and Duration of last scrub gets reset to default when node / glusterd reboots. Additional info:
I am okay to mark this for 3.1.3. But i feel that this has to go as known issue.
(In reply to RamaKasturi from comment #4) > I am okay to mark this for 3.1.3. But i feel that this has to go as known > issue. I'm thinking if we can just stick to showing the corrupted object list along with the corrupted object count, i.e. the statistics which are not accurate as of now are *not shown*. Also, I would wait till the fix goes upstream (we have already started some work on it) to call out which release would this make it to.
(In reply to Venky Shankar from comment #5) > (In reply to RamaKasturi from comment #4) > > I am okay to mark this for 3.1.3. But i feel that this has to go as known > > issue. > > I'm thinking if we can just stick to showing the corrupted object list along > with the corrupted object count, i.e. the statistics which are not accurate > as of now are *not shown*. > > Also, I would wait till the fix goes upstream (we have already started some > work on it) to call out which release would this make it to. venky, are you saying that we will not show any other values other than error count and corrupted objects list in the scrub status output?