Windows 10: ReFS volume with data integrity streams enabled but task scheduler data scrubber doesn't...

Just upgraded to Windows 11 from Windows 10. The ReFS data scrubber task is enabled and I have tried to run it manually. Each scrub should take about an hour given the amount of data that is stored on my single ReFS volume but the task finishes within seconds without an error - unlike what used to happen in Windows 10 Pro for Workstations. The only difference is that the upgraded nuked my mirrored storage space and I didn't have enough storage to extract all the data from it then recreate a new mirror so it's a single, non-storage-spaces ReFS volume now.

:)

 

Has anyone run the Data Integrity Scan on an ReFS volume?

I have tried multiple times to run the Data Integrity Scan from within the Task Scheduler only to receive entries like those below in the Event Log. Integrity is enabled. I have tried with "Enforced" both true and false. Tried with ReFS on simple volume and also with mirrored storage space. Never works. What am I doing wrong?

Error:
Files were skipped during the volume scan.
Files skipped: 310
Volume name: I:\ (\??\Volume{53d99c4e-9ad6-11e8-8448-0cc47ad896dd}\)
First skipped file name: I:
HResult: The specified copy of the requested data could not be read.

Information:
Volume scan completed on I:\ (\??\Volume{53d99c4e-9ad6-11e8-8448-0cc47ad896dd}\)
Bytes repaired: 0x0
Bytes not repaired: 0x3000
HResult: The operation completed successfully.


I'd like to add that the above happens within a minute or two. There were hundreds of files and I know of quite a few that are definitely corrupted.

 

Has anyone run the Data Integrity Scan on an ReFS volume?

Since last fall, ReFS has been implemented in the “Workstations” SKU of Windows 10 Pro. It certainly was not functioning originally, but the good news is that somewhere between then and now, July 2019, some ReFS functionality has appeared (thanks MSFT support). However...

I’ve only done quick and dirty testing with the Data Integrity Scan and it indeed now runs against a mirrored ReFS storage space and it caught some experimentally introduced data errors. This is a huge difference. Recall that last fall the Data Integrity Scan would always fail immediately and find nothing. Back then it was not implemented at all as advertised for the Workstations SKU.

I don’t know the degree and quality with which ReFS functions in Windows 10 Pro for Workstations and I can't spare the hours testing again to determine whether it works as well as on Server (assuming all well even there). I’ll leave that to you others.

I really hope ReFS and Storage Spaces will be a robust solution and I’m eager to have it working for us, but for now we’re running ZFS for data integrity and will reinvestigate ReFS next year. Please add any data corruption testing experiences with ReFS on the Workstations SKU.

 

Will Win 10 Pro ReFS Integrity Streams work after Creator's Update?

I understand that the Win 10 Pro Fall Creator's update removes the ability for Win 10 Pro to create new ReFS volumes but will still permit read/write to existing ReFS volumes. I have a 4 TB ReFS volume that has File Integrity Streams enabled. Will File Integrity
Steams continue to function normally on my existing ReFS volume after the Win 10 Pro Fall Creator's update or will I need to upgrade to Win 10 Pro for Workstation?