Hello,
I don't know if this is the best forum for this as it is powershell, but it is a cluster volume I am creating with 2 VM's in Azure.
When I create a volume for DTC of 500MB, the volume actually gets created as 8GB. I would like to know why and what to do to fix this behavior.
Command I ran:
New-Volume -StoragePoolFriendlyName S2D* -FriendlyName VDiskDBDTC -FileSystem CSVFS_REFS -Size 500MB
Result:
DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining Size
----------- --------------- ---------- --------- ------------ ----------------- ------------- ----
VDiskDBDTC CSVFS Fixed Healthy OK
7.21 GB 7.94 GB
Also, I tried to create it as 1GB and got the following:
PS C:\windows\system32> New-Volume -StoragePoolFriendlyName S2D* -FriendlyName VDiskDBDTC -FileSystem CSVFS_REFS -Size 1GB
DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining Size
----------- --------------- ---------- --------- ------------ ----------------- ------------- ----
VDiskDBDTC CSVFS Fixed Healthy OK
7.21 GB 7.94 GB
The other volumes I created, of various sizes in GB, are the correct sizes. The help page for this command states that you can use MB when specifying size, so I don't know why it won't work correctly.
https://docs.microsoft.com/en-us/powershell/module/storage/new-volume?view=win10-ps
I also attempted this through the GUI, and got slightly different, but still incorrect, results. See screenshots below.
The attempt to create a 500MB virtual disk.
What Get-disk showed after the creation:
What the cluster GUI showed. Note the disk number, and the fact that I already have a disk 10. Wonder what problems THAT will cause. Also note that Powershell does not show a disk
number. What's up with that?
Perhaps I have made mistakes in this creation. I only hope someone can point them out for me and help me correct the problem.
Thanks,
Chris