This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 8%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
We recently had some corruption on one of our file servers and we thought it should have healed itself, though it didn't. We found something interesting that we wanted to get confirmation on. We had a 12 bay server populated with 10 SAS HDD's and 2 SAS SSD's to make a tiered storage spaces virtual disk configured as a mirror. Our volume was formatted as ReFS with Data Deduplication enabled. While all the user files we had the volume had Set-FileIntegrity Enabled, we found the ChunkStore folder and child folders/files did not have this enabled.
In our particular case, the first sign of corruption was a ReFS event stating an object in the chuck store was corrupt and ReFS deleted the file since it could not be repaired. This same event appeared for about 10 chuck objects. Due to deduplication, these same 10 or so objects were apart of 90% of the files on that volume causing all of them to go corrupt.
Does anyone know if the chuck store should have File Integrity enabled, or if this is something automatic perhaps the system processes as part of deduplication?
It appears from the KB's on Integrity Streams that it will only check integrity if the option is enabled on the file.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 8%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hi,
>we found the ChunkStore folder and child folders/files did not have this enabled.
How do you found that?
Because integrity streams carry a performance cost, we recommend leaving integrity streams disabled on performance-sensitive systems.
For more things, please see:
https://video2.skills-academy.com/en-us/windows-server/storage/refs/integrity-streams
https://video2.skills-academy.com/en-us/powershell/module/storage/set-fileintegrity?view=win10-ps
Best Regards,
Daniel
I found this by running powershell as system using PS Exec and getting the results of get-fileintegrity for files under the Chunk Store path.
Furthermore, when enabling File Integrity for a whole volume before any data is written to it, any new items will automatically be set to enabled for File Integrity. Though, this does not apply to the System Volume Information path. No matter the items created there, they still do not have file integrity enabled.
Hi,
According to your description, the issue seems a little strange, we are trying to involve someone more professional to look into this issue, if there's any useful information or suggestions, we'll feedback as soon as possible.
Best Regards,
Daniel