Hi,
I have exactly the same problem, in a quite similar setup :
- Two-node 2019 S2D cluster
- All hardware is hpe from certified HCI list
- Mixed storage (NVME for cache, HDD for capacity)
- Nested mirror-accelerated parity volume
- Formatted with CSVFS_ReFS
- Latest Windows Update and hpe drivers
If I understand well, "Nested mirror-accelerated parity" is a multi-tier setup (it's a mix of NestedMirror tier + NestedParity tier). Then, it seems we are in an unsupported configuration.
In my situation, the cluster hosts Hyper-V virtualization, and the CSVFS contains the VDHX virtual disks. When the scrubbing task starts, it puts the CSV in "suspended mode" (c0e7000b), which generates HDD failures and hadware crashes on some VMs. The "suspended mode" is temporary, so some VMs are not affected. But some others crash severely !
In this setup, NTFS is not an option. I must use ReFS, because it has many advantages for managing VHDX files.
Then, it seems I have two options :
- Keep CSVFS_ReFS volume with nested mirror-accelerated parity, but disable deduplication
- Keep deduplication, but forget mirror-accelerated parity volume, and use single-tier (mirror) volume
Both options will consume far more storage, anyway : S2D mirroring alone is terribly hungry (it eats 4x storage on a 2-node), and in the other hand, deduplication is very efficient when hosting similar VMs (deduplication gain is approx. 65%).
I'll have to check which is the best option for me.
I don't know it it's possible to create a single-tier parity-only volume on a two-node cluster (ie, "parity" for all the HDDs on a server, and "mirroring" between the two nodes).
Anyway, it would be interesting to know if there are plans to support deduplication on ReFS CSV with nested resiliency (multi-tier), because this is the most efficient combination in terms of storage capacity.
Kind regards,