Blog Post

Storage at Microsoft
12 MIN READ

Deep Dive: The Storage Pool in Storage Spaces Direct

Cosmos_Darwin's avatar
Cosmos_Darwin
Icon for Microsoft rankMicrosoft
Apr 10, 2019
First published on TECHNET on Nov 21, 2016 Hi! I’m Cosmos. Follow me on Twitter @cosmosdarwin . Review The storage pool is the collection of ph...
Updated Apr 10, 2019
Version 2.0
biggerpoolthankanye
failover clustering
s2d
Storage Spaces
Storage Spaces Direct
Windows server 2016
i3vi3v's avatar
i3vi3v
Copper Contributor
Nov 07, 2022

Thanks for the great article!

I really understood a lot. However, I still have a lot of questions...

  1. You mention Windows 10, but the article title is about "Storage spaces direct". I've heard that it's very different from the regular "Storage spaces". Is everything this article talks about applicable to a single-node Windows 10 Storage Spaces as well?
  2. Provided that slabs are now placed randomly, is the famous "https://github.com/MicrosoftDocs/azure-docs/issues/8277#issuecomment-392198893" limitation still valid?
  3. If independent 256MB slabs are placed on several different physical disks, and they could be potentially read/written in parallel, to serve somewhat-random-access outstanding IO requests, is the recommendation https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&tabs=windows2016https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&tabs=windows2016 still valid? It sounds like it should only be valid for sequential IO, isn't it?