Red Hat Bugzilla – Bug 1277126
[New] - Files in a tiered volume gets promoted when bitd signs them
Last modified: 2016-09-17 11:41:32 EDT
Description of problem:
Have an EC volume as cold tier and attached replicate volume as hot tier and enabled bitrot on the volume. Once files are not accessed they get demoted and bitd tries to sign the files. Once the files are signed it gets promoted to hot tier. If the attrs of a file changes, tiering should not promote the file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a EC distribute disperse as cold tier and replicate volume as hot tier.
2. Mount the volume using fuse mount and create some files in the volume
3. Once the files get demoted to cold tier, bitd waits for 120sec to sign the file.
Once the file is signed, file gets promoted to hot tier.
File should not get promoted as there is no change in the contents of the file.
sos reports can be found at the link below:
Files should not get heated up for any of the internal ops going on the volume
Cannot test scrubber because, signature is heating up the files and when a file is corrupted from the backend, tiering will promote the file and signature is calculated again. So by the time scrubber comes and checks the file signature it will match with the signature and what scrubber calculated, so file will never be marked as bad.
Patch 60999 adds bitrot fops to the "internal" list, fops on that list are ignored for heat calculations.
Verified and works fine with build glusterfs-3.7.5-6.el7rhgs.x86_64.
When bitd signs the files , files does not get promoted to hot tier.
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.