Q1: When we create a 2-way mirrored virtual disk in Storage Pool by GUI, why the maximum size is much smaller than it should be?
Example: A Storage pool with 4 physical disks (2x8GB + 2x5GB). The size of a 2-way mirrored virtual disk should be 13GB (Figure 1).
Figure 1
However system shows only 6GB in creating the virtual disk (Figure 2).
Figure 2
Cause: By default, Windows Server UI will optimize the creation for performance. Thus it will be a 2-column, 2-copy storage space.
Solution: In order to get a 1-column storage space, we need to create it with PowerShell cmdlet:
New-VirtualDisk –FriendlyName MySpace –StoragePoolFriendlyName MyPool –NumberOfColumns 1 –UseMaximumSize