I use several ReFS volumes , either on one-way or two-way mirrored storage spaces under Windows Server 2012R2.
The description of the automated 'scrubbing' on TechNet seems a bit unclear to me. Microsoft explains:
Integrity. ReFS stores data in a way that protects it from many of the common errors that can normally cause data loss. When ReFS is used in conjunction with a mirror space or a parity space, detected corruption—both metadata and user data, when integrity streams are enabled—can be automatically repaired using the alternate copy provided by Storage Spaces. In addition, there are Windows PowerShell cmdlets (Get-FileIntegrity andSet-FileIntegrity) that you can use to manage the integrity and disk scrubbing policies.
And further on:
ReFS can automatically correct corruption on a parity space when integrity streams are enabled to detect corrupt data and because ReFS examines the second (and third) copies that the data parity spaces contain. ReFS then uses the correct version to correct the corruption.
 Note |
|---|
| ReFS can already detect corruption on mirrored spaces and automatically repair those corruptions. |
Does this mean the file attribute "FileIntegrity" has to be set to "on" in order for automatic scrubs (of user data) and automatic correction (of user data) an mirrored spaces to take place--or not?
If the answer is that "FileIntegrity" has to be explicitly set to "on", what happens with new files copied into or created in an existing folder structure for which I set "FileIntegrity" to on? Do I see it correctly that "FileIntegrity" is off for new files by default?
So do I have to run a PowerShell command like
PS C:\> Get-Item-Path 'H:\Temp\*' | Set-FileIntegrity-Enable $True
(source)
every time a new file might have been copied into the folder structure of "H:\Temp\" in order to activate automatic scrubbing and repairing forall files in this folder?
Thanks for your comments.