7

NTFS is the only option when Parity is selected as the resiliency type. I thought ReFS was suppose to replace NTFS? I am trying to create a storage space to use for network file share.

enter image description here

enter image description here

  • What is your specific question? Storage Spaces is basically a Microsoft software RAID 1 solution. If you want parity then you can't use Storage Spaces and would have to use a RAID 3 or similar solution. – Ramhound Sep 3 '15 at 14:01
  • @Ramhound That’s obviously not correct. Storage Spaces supports RAID-5-ish redundancy, which is called “Parity”. That being said, I strongly recommend not using ReFS. It has some stability issues and if it fails, you’re SOL. I almost lost multiple TiB, luckily it started working again after some reboots. – Daniel B Sep 3 '15 at 14:05
  • @DanielB - I only said RAID-1 because the screenshot indicates it only does mirroring without parity. I said RAID-3 since that is the first RAID level which supports both. I wasn't aware Storage Spaces was considered to be RAID-5. Which begs the questions, if that's the case, what is the question again? – Ramhound Sep 3 '15 at 14:11
  • 1
    I'm asking if I can use ReFS with parity type resiliency, similar to the traditional RAID5. – rocfob Sep 3 '15 at 14:17
  • Well, I can reproduce this in Windows 8.1: It’s only available with 2/3-way mirrored volumes. – Daniel B Sep 3 '15 at 20:50
1

Format with ReFS is turned off by default in client versions of Windows (8/8.1/10). You can turn it on modifying registry keys:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT]
"AllowRefsFormatOverNonmirrorVolume"=dword:00000001

and

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"RefsDisableLastAccessUpdate"=dword:00000001

after that you can format any suitable volume with ReFS

  • This kinda works on Windows 10 Anniversary edition (v1607, b14393). It will let you format volume with ReFS and create parity ReFS storage space. Both are very unstable, obviously it is disabled for a reason. – Vlastimil Ovčáčík Oct 20 '17 at 19:51
  • @Vlastimil Ovčáčík what do you mean 'VERY unstable'? It works for more than 5 years, since Windows 8. The onyl reason I see why it's disabled - separating features between server and client version, like it was in many versions before. But such separating is just symbolical, as you can see. It was not completely disabled. Like I said - like in many versions before. Moreover - [using Storage Spaces in conjunction with ReFS gives additional errors recoverability][1] [1]: technet.microsoft.com/en-us/library/hh831724(v=ws.11).aspx – Wolfrevo Cats Oct 24 '17 at 0:13
  • I meant the process of creating ReFS volume or storage space is unstable, that means formatting via GUI and CLI always failed for me, but I was able to create ReFS volumes/storage space with PowerShell. I wasn't judging ReFS itself. – Vlastimil Ovčáčík Oct 24 '17 at 7:05
  • @Vlastimil Ovčáčík that's weird. Works fine for me on many workstations with Windows 8.1 and Windows 10 in different disks and volumes configurations – Wolfrevo Cats Oct 24 '17 at 23:34
  • RefsDisableLastAccessUpdate is performance optimization, you don't need it to get ReFS working, but NTFS has it enabled by default since Windows Vista and ReFS got it enabled by default since Windows 10 Pro for Workstations. I suppose same applies for server editions. – Vlastimil Ovčáčík Oct 26 '17 at 9:58
1

According to discussion at Storage Spaces, Parity and ReFS

  • ReFS in storage spaces is available only for two-way and three-way mirroring until Windows 10 Anniversary update incl.
  • Creators update brought support for ReFS parity storage space
  • Fall Creators update removes ReFS entirely from storage spaces
  • Windows 10 version history may be handy. – Vlastimil Ovčáčík Oct 20 '17 at 20:16
  • "not sure about ReFS simple storage space (anyone can comment on that?)" - If you are not sure of something best to leave it out of your answer, otherwise, comments like that are just unnecessary noise. – Ramhound Oct 26 '17 at 17:50
-1

You may not be able to select parity, as ReFS has Built-in resilience as NTFS does not have the same.

ReFS creates 64-bit checksum, with this in mind the mirrored volumes self check and heal where possible.

I would say this is why you cannot select a parity option for ReFS.

  • 1
    this is incorrect as windows server 2016 supports refs over parity storage space – Robert Ivanc Feb 16 '17 at 15:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.