PrimoCache 3.0.9 - Refs - Data Integrity Scan
Posted: Fri Feb 22, 2019 6:08 pm
Hello, I have an issue to address concerning refs and PrimoCache.
I have a refs volume set up with file integrity streams enabled on storage spaces.
File integrity streams and metadata integrity streams are supposed to be checked for actual integrity on refs volumes via a task in the task scheduler named “Data Integrity Scan”
If I trigger a Data Integrity Scan and the refs volume is setup in PrimoCache for read or write caching I get the following two errors in the Event Viewer
Error 57
Volume metadata scrub operation failed.
Volume name: Y:
Metadata reference: 0x204
Range offset: 0x0
Range length (in bytes): 0x0
Bytes repaired: 0x0
Bytes not repaired: 0x3000
Error 24
Files were skipped during the volume scan.
Files skipped: 3
Volume name: Y:\ (\??\Volume{a22c0f2e-30fb-11e9-bf16-90e6ba776a76}\)
First skipped file name: Y:
HResult: The specified copy of the requested data could not be read.
Status: The specified copy of the requested data could not be read.
(Note:The number of files skipped varies depending on the files that are on the volume)
However, if the refs volume is not set up in PrimoCache for read/write caching then Data Integrity Scan completes its duty successfully and the Event Viewer reports, hopefully, a success message.
Volume scan completed on Y:\ (\??\Volume{a22c0f2e-30fb-11e9-bf16-90e6ba776a76}\)
Bytes repaired: 0x0
Bytes not repaired: 0x0
HResult: The operation completed successfully.
Please note that I have tested this issue on three pcs and the results are consistent.
I have a refs volume set up with file integrity streams enabled on storage spaces.
File integrity streams and metadata integrity streams are supposed to be checked for actual integrity on refs volumes via a task in the task scheduler named “Data Integrity Scan”
If I trigger a Data Integrity Scan and the refs volume is setup in PrimoCache for read or write caching I get the following two errors in the Event Viewer
Error 57
Volume metadata scrub operation failed.
Volume name: Y:
Metadata reference: 0x204
Range offset: 0x0
Range length (in bytes): 0x0
Bytes repaired: 0x0
Bytes not repaired: 0x3000
Error 24
Files were skipped during the volume scan.
Files skipped: 3
Volume name: Y:\ (\??\Volume{a22c0f2e-30fb-11e9-bf16-90e6ba776a76}\)
First skipped file name: Y:
HResult: The specified copy of the requested data could not be read.
Status: The specified copy of the requested data could not be read.
(Note:The number of files skipped varies depending on the files that are on the volume)
However, if the refs volume is not set up in PrimoCache for read/write caching then Data Integrity Scan completes its duty successfully and the Event Viewer reports, hopefully, a success message.
Volume scan completed on Y:\ (\??\Volume{a22c0f2e-30fb-11e9-bf16-90e6ba776a76}\)
Bytes repaired: 0x0
Bytes not repaired: 0x0
HResult: The operation completed successfully.
Please note that I have tested this issue on three pcs and the results are consistent.