Spaces can have the attribute of being parity spaces, in which case parity information about data is stored as well to aid in data-regeneration when a physical drive fails. Once again slabs are used as an intermediate storage construct and striped. Parity spaces take up less space than a mirrored copy of the data, but involve more random I/O in their operation.
When a drive fails, there is automatic recovery of the lost data, using parity we suppose, and a regeneration of the parity data, using the same general principles as with a mirror-spaces recovery operation.
You can have parity spaces and mirror spaces carved out from the same storage pool with the slabs intermingled. Parity spaces appear to be roughly equivalent to RAID 5 (single drive failure) and RAID 6 (dual drive failure protection).
Storage spaces can be created using the PowerShell CLI. This is okay for storage admins, but – to this writer's mind – frankly ghastly for small businesses and home users. (Sinofsky and Nagar's blog post provides examples.)
Far better to use the Control Panel and get a GUI approach, which is simpler and cleaner. Again the blog post gives examples. You select the System and Security option, then Storage Spaces.
Storage Spaces and the control panel
So, what do we think about Storage Spaces? First of all, virtualising storage is a good idea, and automating data resilience and recovery from drive failure is very sensible. Perhaps users with Storage Spaces will have less need to rely on backup software or to buy self-protecting external storage arrays such as Drobos.
However, the protection, although RAID-like, is not RAID and not hardware-assisted. We have no information on recovery timings other than that it happens automatically in the background, which is good. Clearly, the larger the capacity of the failed drive, the longer the recovery time will be. Perhaps storage spaces are better carved out from pools made of many small drives than a few large drives.
Also, recovery uses host CPU cycles and this may, in a machine with few spare cycles, affect overall responsiveness.
A third overall point is that users will have to know when to use basic storage spaces, mirror spaces, and parity spaces. Storage user life is simpler in Drobo-land where there are fewer choices. You might feel that Microsoft is trying to cover too many bases with a Storage Spaces concept that covers all the ground and requirements between home users and enterprise data centres.
Storage Spaces is somewhat like ZFS, although it has no deduplication and lacks other ZFS features. However, it is a start – and Microsoft will probably add features such as snapshots, replication, deduplication, and, maybe, compression. El Reg also thinks that there could be a Hyper-V virtualisation angle to this – and more is to come. ®
Wow! What an innovation!
What an innovative and unique idea from Microsoft! Let me see if I understand it:
You turn a disk drive into a, what do you call it, a physical volume
You group those physical volumes into some form of logical volume
You create virtual disks from those logical volumes, and those virtual disks can spread across different physical disks, and can survive a disk failing.
What brilliant fellows Microsoft are! Wait - my Linux server just emailed me, something about a failure in LVM, a drive down, and falling back to the spare...
Too late, I activated a proxy on my gateway and blocked 2788 ad servers, inc ad.doubleclick.net, no more annoyances and no ad revenue for the reg from my office.
Maybe the reg should think about their readers before accepting _disrupting_ ads.
RE: But the big question is ...
Taking a dig at the incredibly annoying M$ cloud ad at the top of all The Register pages, which makes the whole page jump up just as you start reading an article? Agree completely - make it static or take it off.