ReFS can not be automatically correct in the Parity Space ?

Question

I had to test
the automatic correction of ReFS on parity space, but did not cause the automatic correction is performed any times I try.
ReFS does not corrected even if tried on dual parity.
I tried,
Three VHD atatched to Windows Server 2012 R2 Virtual Machine.
Create pool, parity space, format ReFS on VM.
Write data to ReFS.
Shutodown VM.
Modify the data portion I wrote.
Start VM.
Read that data.
The expected automatic correction but it was not carried out.
Log Name: System
Source: ReFS
Date: 2014/01/10 13:48:43
Event ID: 133
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: WIN-T431BH574GD
Description:
The file system detected a checksum error and was not able to correct it. The name of the file or folder is "E:\New Text Document.txt".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ReFS" Guid="{036647D2-2FB0-4E32-8349-3F5C19C16E5E}" />
<EventID>133</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-01-10T04:48:43.347097300Z" />
<EventRecordID>1398</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="148" />
<Channel>System</Channel>
<Computer>WIN-T431BH574GD</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ObjectNameLength">24</Data>
<Data Name="ObjectName">E:\New Text Document.txt</Data>
<Data Name="FailureReason">0xc0000470</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-DataIntegrityScan/Admin
Source: Microsoft-Windows-DataIntegrityScan
Date: 2014/01/10 13:50:07
Event ID: 55
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: WIN-T431BH574GD
Description:
File data scrub operation failed. File name: E:\New Text Document.txt; range offset: 0x0; range length (in bytes): 0x4000; bytes repaired: 0x0; bytes not repaired: 0x4000; status: A data integrity checksum error occurred. Data in the file stream is corrupt..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DataIntegrityScan" Guid="{13BC4371-4E21-4E46-A84F-8C0FFB548CED}" />
<EventID>55</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-01-10T04:50:07.206437000Z" />
<EventRecordID>24</EventRecordID>
<Correlation />
<Execution ProcessID="2976" ThreadID="3044" />
<Channel>Microsoft-Windows-DataIntegrityScan/Admin</Channel>
<Computer>WIN-T431BH574GD</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FileNameLength">24</Data>
<Data Name="FileName">E:\New Text Document.txt</Data>
<Data Name="InternalFileReference">0x0</Data>
<Data Name="FileOffset">0x0</Data>
<Data Name="Length">0x4000</Data>
<Data Name="BytesRepaired">0x0</Data>
<Data Name="BytesFailed">0x4000</Data>
<Data Name="Status">0xc0000470</Data>
</EventData>
</Event>
Can be automatically corrected ReFS what if situation?
I used VHDs here.
https://www.dropbox.com/s/zalzl5132ysr9hr/Archive.zip
ReFS_parity_pool1.vhdx  Consistency pool member
ReFS_parity_pool2.vhdx  Consistency pool member
ReFS_parity_pool3.vhdx  Consistency pool member
Corrupted_parity_pool1.vhdx  Same as ReFS_parity_pool1
Corrupted_parity_pool2.vhdx  Same as ReFS_parity_pool2
Corrupted_parity_pool3.vhdx  Copy of ReFS_parity_pool3, modified one byte.
Mirror Space always works well.

Answer 1

Hi,
Correct me if I'm wrong.
You create 3 VHD(x) files on host server and connected them to a VM, which act as physical server on VM.
Using the 3 VHD(x), you created a storage pool in VM and created a parity virtual disk.
Then you wrote files, shutdown VM and edit one of these VHD(x) which emunicate the parity disk corruption. It cannot be fixed automatically by ReFS file system.
From the reply I got, VHD files will not able to be fixed for such issue - So I assume that using VHD files in VM for the test may not get the correct result. If available it is more recommended to test with physical hard disk. 
If you have any feedback on our support, please send to [email protected]