I use storage pools since server 2012 R2 and think its a good solution.
But there are some limitations on server 2012 R2 (re-balance) where no longer exists on server 2016 and 2019. Now I have build a new server based on server 2019 Hyper-V.
The migration was quite easy:
- Take the storage pool offline on server 2012 R2
- Install server 2019
- Attach the storage pool and take it online
- migrate it to version server 2019
- works!
But now I have start to copy some files to the storage pool and notice that the memory consume in the non-paged-pools grows. After copy of 1TB the pool is 1GB larger. After on or two days the server crashes with out of non-paged-pool memory.
The analyse with poolmon identify the tag "Sp**".
I have found in different forums that there was a problem on server 2016 with the spaceport.sys using ReFS.
What I have try:
- delete virtual drive (ReFS), recreate virtual drive NTFS
- delete alls virtual drives, delete storage pool, recreate virtual drive
But I always end after copy of 5TB files in a non-paged-pool whit a size of more than 10GB.
Not sure, but I think there must be a memory leak in the spaceport.sys on server 2019.
On the hardware side I use an SuperMicro board with an intel C236 chipset.
Attached 4 SATA harddisk with same size attached to the pool.
After this I have make additional tests:
- Hyper-V Server 2019 with Microsoft standard AHCI drivers
- Hyper-V Server 2019 installed on a different hardware
- Hyper-V Server 2019 installed on VMWare-Workstation
- Server 2019 Standard (GUI) installed on VMWare-Workstation
In all cases I have build an new StoragePool based on 3 disk and create a virtual harddisk of type mirror.
Then I have copied some files (114 GB) to the virtual harddisk on the StoragePool and repeat this 3 times.
I can notice that after each copy process the non-paged-pool grows by 20MB.
Conclusion:
on my point of view, I think there is a memory leak inside the storage space feature (Windows 1809)
