I have a problem with Bitrot/scrubing/healing, Someone please help
Description of Problem:
1. When a file is corrupted,
a) The scrub is sometimes identifying that the file is corrupted (I can see the entry when the scrub status is checked), Can see log for corrupt entry in log and the file is not self-healing over time
b) The scrub sometimes not writing an entry in the scrub status but has healed automatically - No log for self-heal is seen
Why there is a difference in the process of scrubbing for file corruption, how this scrubbing and healing is queued?
2. Our Gluster volume is set with scrub frequency - Daily
a) Sometimes the number of skipped files is very high, for example, if we have 100 files it is skipping 88 files.
b) The count of skipped files varies on a daily basis, sometimes 88, sometimes 30 etc.., Why?
c) Suppose if, before completing the current scrubbing process, the next cycle of scrubbing is due or triggered, will the current scrubbing process skips the remaining file and fulfill the new triggering or will it wait for the current scrubbing process to get complete and fulfill the new trigger?
Please clarify
Description of Problem:
1. When a file is corrupted,
a) The scrub is sometimes identifying that the file is corrupted (I can see the entry when the scrub status is checked), Can see log for corrupt entry in log and the file is not self-healing over time
b) The scrub sometimes not writing an entry in the scrub status but has healed automatically - No log for self-heal is seen
Why there is a difference in the process of scrubbing for file corruption, how this scrubbing and healing is queued?
2. Our Gluster volume is set with scrub frequency - Daily
a) Sometimes the number of skipped files is very high, for example, if we have 100 files it is skipping 88 files.
b) The count of skipped files varies on a daily basis, sometimes 88, sometimes 30 etc.., Why?
c) Suppose if, before completing the current scrubbing process, the next cycle of scrubbing is due or triggered, will the current scrubbing process skips the remaining file and fulfill the new triggering or will it wait for the current scrubbing process to get complete and fulfill the new trigger?
Please clarify