You can safely ignore this thread, since it’s just my complain on technology and how people trying to be smart …
Apparently it was a great article, BUT …
I HATE the overhead of MS storage pool, it’s slow and used almost 30GB just for the 1440GB pool, theoretically i just lost a plot to the storage overhead, so i started my journey to find a better way …
- At first, i thought a .vhd file mounted as a physical disk, which could be converted into a dynamic disk, then you can just make a spanned volume across the vhd files to make a storage pool, but then i realized that Microsoft outsmarted me by prevent the vhd file from mounted as dynamic disk, you can try to use another tools to make the vhd file a dynamic disk, but then it will failed to mount using windows way.
- The linux way would be easy since you can just make loop devices from the excess space, then merge them using either mdadm/zfs, but i had to shake it off because all plot drives are NTFS and there’s no easy to convert them into linux format, and NTFS reading from linux is such a pain to your CPU.
- I looked for the 3rd party solution, but there’s pretty much … none. Some software like ImDisk only emulate a partition, not a disk, not a spanned volume. Some others can actually emulate a real harddrive but have their own limitations :
- OSFMount can emulate 9 physical disk and no more, guess some people in their company is very smart and decided to support 9 instead of 999 drives just because they can. Theoretically the driver code don’t care if you mount 1 or 100 disks.
- TotalMount has the same limitation.
- DAEMON Tools is not free, but their demo version can’t mount dynamic vhd
- ArsenalImageMounter can mount 1 fully functional vhd, the rest are readonly.
- A lot of crappy tools.
- A lot of untested commercial tool.
- A light shown up : winspd can mount as much vhd as you want, but quickly fades away : their user mode code ate a lot of cpu and are quite slow, <10MB/s.
- Another bigger light shown up, a tool that microsoft made since they introduced the VSS : the vstorcontrol/virtualstoragevss that is available on every WindowsSDK, but then also fades away - Microsoft outsmarted me again by limit the volume size at 512MB.
In the end i still stuck with stupid storage pool that had became readonly because i accidentally made the virtual volume size bigger than the pool size and there is no way to shrink it because Microsoft outsmarted the whole world by decide that disk shrinking is not necessary.
There are some 3-way intersections on my journey, like using linux/windows VM to handle the excess space, but they’re all stupid idea …