Server 2019 (Windows 1809) spaceport.sys non-paged-pool memoryleak?

%3CLINGO-SUB%20id%3D%22lingo-sub-531312%22%20slang%3D%22en-US%22%3EServer%202019%20(Windows%201809)%20spaceport.sys%20non-paged-pool%20memoryleak%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-531312%22%20slang%3D%22en-US%22%3E%3CP%3EI%20use%20storage%20pools%20since%20server%202012%20R2%20and%20think%20its%20a%20good%20solution.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EBut%20there%20are%20some%20limitations%20on%20server%202012%20R2%20(re-balance)%20where%20no%20longer%20exists%20on%20server%202016%20and%202019.%20Now%20I%20have%20build%20a%20new%20server%20based%20on%20server%202019%20Hyper-V.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20migration%20was%20quite%20easy%3A%3C%2FP%3E%3CUL%3E%3CLI%3ETake%20the%20storage%20pool%20offline%20on%20server%202012%20R2%3C%2FLI%3E%3CLI%3EInstall%20server%202019%3C%2FLI%3E%3CLI%3EAttach%20the%20storage%20pool%20and%20take%20it%20online%3C%2FLI%3E%3CLI%3Emigrate%20it%20to%20version%20server%202019%3C%2FLI%3E%3CLI%3Eworks!%3C%2FLI%3E%3C%2FUL%3E%3CP%3EBut%20now%20I%20have%20start%20to%20copy%20some%20files%20to%20the%20storage%20pool%20and%20notice%20that%20the%20memory%20consume%20in%20the%20non-paged-pools%20grows.%20After%20copy%20of%201TB%20the%20pool%20is%201GB%20larger.%20After%20on%20or%20two%20days%20the%20server%20crashes%20with%20out%20of%20non-paged-pool%20memory.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20analyse%20with%20poolmon%20identify%20the%20tag%20%22Sp**%22.%3C%2FP%3E%3CP%3EI%20have%20found%20in%20different%20forums%20that%20there%20was%20a%20problem%20on%20server%202016%20with%20the%20spaceport.sys%20using%20ReFS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20have%20try%3A%3C%2FP%3E%3CUL%3E%3CLI%3Edelete%20virtual%20drive%20(ReFS)%2C%20recreate%20virtual%20drive%20NTFS%3C%2FLI%3E%3CLI%3Edelete%20alls%20virtual%20drives%2C%20delete%20storage%20pool%2C%20recreate%20virtual%20drive%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3EBut%20I%20always%20end%20after%20copy%20of%205TB%20files%20in%20a%20non-paged-pool%20whit%20a%20size%20of%20more%20than%2010GB.%3C%2FP%3E%3CP%3ENot%20sure%2C%20but%20I%20think%20there%20must%20be%20a%20memory%20leak%20in%20the%20spaceport.sys%20on%20server%202019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20hardware%20side%20I%20use%20an%20SuperMicro%20board%20with%20an%20intel%20C236%20chipset.%3CBR%20%2F%3EAttached%204%20SATA%20harddisk%20with%20same%20size%20attached%20to%20the%20pool.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20this%20I%20have%20make%20additional%20tests%3A%3C%2FP%3E%3CUL%3E%3CLI%3EHyper-V%20Server%202019%20with%20Microsoft%20standard%20AHCI%20drivers%3C%2FLI%3E%3CLI%3EHyper-V%20Server%202019%20installed%20on%20a%20different%20hardware%3C%2FLI%3E%3CLI%3EHyper-V%20Server%202019%20installed%20on%20VMWare-Workstation%3C%2FLI%3E%3CLI%3EServer%202019%20Standard%20(GUI)%20installed%20on%20VMWare-Workstation%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIn%20all%20cases%20I%20have%20build%20an%20new%20StoragePool%20based%20on%203%20disk%20and%20create%20a%20virtual%20harddisk%20of%20type%20mirror.%3C%2FP%3E%3CP%3EThen%20I%20have%20copied%20some%20files%20(114%20GB)%20to%20the%20virtual%20harddisk%20on%20the%20StoragePool%20and%20repeat%20this%203%20times.%3C%2FP%3E%3CP%3EI%20can%20notice%20that%20after%20each%20copy%20process%20the%20non-paged-pool%20grows%20by%2020MB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConclusion%3A%3C%2FP%3E%3CP%3Eon%20my%20point%20of%20view%2C%20I%20think%20there%20is%20a%20memory%20leak%20inside%20the%20storage%20space%20feature%20(Windows%201809)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-531312%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692614%22%20slang%3D%22en-US%22%3ERe%3A%20Server%202019%20(Windows%201809)%20spaceport.sys%20non-paged-pool%20memoryleak%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692614%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20the%20issues%20is%20fix%20with%20the%20cumulative%20update%202019-06.%3C%2FP%3E%3CP%3EI%20have%20install%20it%20and%20copy%20some%20data.%20After%20copy%201TB%20I%20see%20a%20growing%20of%2010MB%20on%20the%20non-paged%20pool%20SP**.%20Not%20nothing%2C%20but%20much%20better%20than%201GB%20per%201TB%20data.%3C%2FP%3E%3CP%3ECan%20some%20other%20confirm%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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)

 

1 Reply

I think the issues is fix with the cumulative update 2019-06.

I have install it and copy some data. After copy 1TB I see a growing of 10MB on the non-paged pool SP**. Not nothing, but much better than 1GB per 1TB data.

Can some other confirm this?