Considering the following Wikipedia information and other data found on the internet as well, we decided to implement Windows 10 Storage Spaces Two-Way Mirror using plain NTFS, but wanted to know if the landscape has improved for recovery of this relatively new file system.
What is below is the excerpt from Wikipedia that this question is referencing (they made it sound like an impossible problem to solve):
ReFS -- Stability and known problems https://en.wikipedia.org/wiki/ReFS#Stability_and_known_problems
Issues identified or suggested for ReFS, when running on Storage Spaces (its intended design), include:
Adding thin-provisioned ReFS on top of Storage Spaces (according to a 2012 pre-release article) can fail in a non-graceful manner, in which the volume without warning becomes inaccessible or unmanageable. This can happen, for example, if the physical disks underlying a storage space became too full. Smallnetbuilder comments that, in such cases, recovery could be "prohibitive" as a "breakthrough in theory" is needed to identify storage space layouts and recover them, which is required before any ReFS recovery of file system contents can be started; therefore it recommends using backups as well.
Even when Storage Spaces is not thinly provisioned, ReFS may still be unable to dependably correct all file errors in some situations, because Storage Spaces operates on blocks and not files, and therefore some files may potentially lack necessary blocks or recovery data if part of the storage space is not working correctly. As a result, disk and data addition and removal may be impaired, and redundancy conversion becomes difficult or impossible.
There are no tools to repair or recover a ReFS filesystem. Third party tools are dependent on reverse engineering the system and (as of 2014) few of these exist..
Also, can Windows 10 boot to a Two-Way Storage Spaces? Thanks.