Storage Pools - too much overhead?
i'm experimenting storage pools in windows 2012 r2 vm , seeing interesting disk space utilization / overhead i'm not sure expected.
added 2 10 gb physical disks vm. the system detects each 10.0 gb.
created storage pool these 2 disks. after creation, storage pool reports capacity of 18.5 gb 18.0 gb free. so, i've lost 2 gb (10%).
if use pool create "fixed" virtual disk using "simple" layout, max vd size 16 gb. the pool still reports capacity of 18.5 gb shows 1.0 gb free.
if delete vd , use same pool create "fixed" virtual disk using "mirror" layout, max vd size 7 gb. the pool still reports capacity of 18.5 gb shows 1.5 gb free.
using 20 gb of disk , ending 16 gb (simple layout) or 7 gb (mirror layout) seems lot of wasted disk space. is expected?
thanks!
i've figured out *part* of mystery.
when virtual disk created, there's default setting uses of space create write cache. if use powershell cmdlet create pool, can 0 default. in case, "simple" layout max vd 18 gb (instead of 16 gb) , "mirror" layout max vd 8 gb (instead of 7 gb).
this bit better i'm still curious why (a) lose 2 gb when creating storage pool , (b) "mirror" layout isn't using full pool space "simple" layout is. i'm guessing (b) might space used "dirty region tracking" feature mirror spaces use simple spaces not.
Windows Server > File Services and Storage
Comments
Post a Comment