I have done a lot of experimenting with storage space (and like them) and am considering ReFS for use on a photo editing workstation where there are lots of rarely used images that I want to protect from long term bit rot.
I am doing this in Windows 10 AU with Powershell.
Some specific questions:
1) If I set the File Integrity flag for a file, and at some point a checksum discrepancy is found, what specifically occurs? Does it auto-repair from storage space redundancy? Does it record this fact anywhere? How are any failures to repair reported?
1a) Is there any way to simulate such a failure, easily? And how and when (and can you force) an integrity check scan?
2) It appears the File Integrity default can be set at format time for a volume. I cannot find any way to change it on a volume (specifically the default, I can see how to change individual files). Is there a way to change the default short of re-format? Is the default doing anything beyond just setting the default for files (i.e. is it doing something more at the volume level)?
And final more subjective question:
3) The performance suffers a lot with File Integrity set (on SSD 2x2 mirror). During initial image uploads and subsequent editing speed is important, later not much so. My thinking is to disable file integrity as default, but run a brief script that takes any file over a week old (basically when a given shoot has been edited and published), and sets file integrity on it for longer term protection. Obviously some risk in that interim, but that aside, is there any downside to this approach? (Specifically to not having the volume itself flagged just individual files?)
Thanks.
Linwood