Okay, thanks; I'll be waiting, then.
For reference, here is the power shell code that created the dual parity vDisk containing the missing vhdx half a year ago:
#controllers = 1x LSI SAS2 9207-8i + 1x LSI SAS2 9217-8i (both in HBA mode with newest firmware v20.00.07.00).
#$journalSSDs = 3 SSDs (2x
Intel
SSDSC2BB24 + 1x
Intel
SSDSC2BB48)
#$HDDs = 10 HDDs (2x Toshiba HDWE160 6TB CMR + 2x Seagate ST8000DM005 8TB CMR + 6x Seagate ST8000AS0002 8TB SMR)
$sPool
= "BackupHost StoragePool"
New-StoragePool `
-StorageSubsystemFriendlyName
"Windows Storage*" `
-FriendlyName
$sPool `
-PhysicalDisks ($HDDs
+ $journalSSDs) `
;
Set-StoragePool
-FriendlyName $sPool
-IsPowerProtected $True
#have UPS.
$sVDiskFriendlyName
= "vDisk(jdMirr.1c,dPar.(7+3)c.64GBWBC.16MBiL)).ReFS.4k";
$WBC4mirrAccParity
= 64GB;
$parityVDisk
= Get-StoragePool
$sPool |
New-VirtualDisk -FriendlyName
$sVDiskFriendlyName `
-MediaType
HDD `
-FaultDomainAwareness
PhysicalDisk `
-ResiliencySettingName
Parity -PhysicalDiskRedundancy
2 `
-NumberOfColumns (7+3)
`
-Size 44035GB `
-ProvisioningType
Thin `
-Interleave 16MB `
-WriteCacheSize
$WBC4mirrAccParity `
;
#<-Note: a larger write cache and interleave mean longer pauses for individual HDDs in sustained write phases => higher overall throughput, as individual SMR disks utilize these pauses for moving their data from CMR to shingled magnetic recording regions.
$sVolumeLabel
= "SA (WBC-acc dParity.10c)";
$driveLetter
= "R:";
$parityReFSVol
= New-Volume
-FriendlyName $sVolumeLabel `
-DiskUniqueId
$parityVDisk.UniqueId `
-FileSystem
ReFS `
-AccessPath
$driveLetter `
;
Get-Item
-Path $driveLetter\
| Set-FileIntegrity
-Enable $true
Get-Item -Path
$driveLetter\
| Get-FileIntegrity
Get-ChildItem
-Path $driveLetter\
-Recurse |
Set-FileIntegrity -Enable
$true
Get-ChildItem -Path
$driveLetter\
-Recurse |
Get-FileIntegrity |
ft Enabled,
Enforced,
FileName
This ReFS volume with enabled file integrity stored the now missing VHDX containing our measurement data archive. The vhdx inner file system was also ReFs, but I left FileIntegrity at default here, i.e. disabled. This vhdx was a shared network drive; worked
well for about half a year until now... :/
Notably, this storage pool contains another virtual disk (also with ReFS and enabled file integrity, but only single-parity). Meanwhile, I backupped its contents (also several TBs) to another computer without any errors, although it resides on the same physical
disks...
