Bug 1296808 - [New] - When RHGS nodes are upgraded from 3.1.1 to 3.1.2 scrub status does not show the files which were corrupted before upgrade.
[New] - When RHGS nodes are upgraded from 3.1.1 to 3.1.2 scrub status does n...
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: bitrot (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Kotresh HR
storage-qa-internal@redhat.com
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-08 02:40 EST by RamaKasturi
Modified: 2017-03-25 12:26 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description RamaKasturi 2016-01-08 02:40:56 EST
Description of problem:
When RHGS nodes are upgraded from 3.1.1 to 3.1.2 scrub status does not list the files which were corrupted before the system was upgraded even after the scrubber is run.

Version-Release number of selected component (if applicable):
glusterfs-3.7.5-14.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have two RHGS nodes of 3.1.1 
2. Create volume and enable bitrot on the volume and set the scrubber frequency to hourly.
3. Fuse mount the volume and create some files.
4. Wait for 120 secs, and edit the file from backend so that it will be marked as bad.
5. Once the file is marked bad, update the system to 3.1.2.
6. set the glusterd opversion to 30706
6. Wait for one hour for the scrubber to run.
7. Run the command 'gluster vol bitrot <vol_name> scrub status'

Actual results:
scrub status does not list the files which were corrupted before the system was upgraded even after the scrubber is run.

Expected results:
scrub status should list the files which were corrupted before upgrade.

Additional info:

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