Hi, I've recently migrated my data (8,5Tb) from Windows Home Server v1 (Drive Extender) to Windows 8 Pro (Storage Spaces parity mode).
The pool is made by 11x2Tb HDs and the Storage Space is 20Tb thin provisoned to ensure me a 8192 cluster size for further expasion.
What I've noticed is that I have by now 2,5Gb of Non-Paged-Pool memory locked of my 16 Gb Ram installed!
Using poolmon.exe I found that the non paged pool is allocated to a proces with TAG "SpBu" that it seems to be related to StorageSpaces driver?!
It seems also that the more files I add to the SSpace the more non paged pool grows btw, if I free space from the SSpace the non paged pool decreases.
So, my question is:
Is it a normal behaviour that Storage Spaces needs to allocate so mouch memory (2,5Gb for 8,5Tb of data in parity mode) or I have some other problem maybe related to my additional Promise controller driver?
Andrea Bernacchini
View the full article
The pool is made by 11x2Tb HDs and the Storage Space is 20Tb thin provisoned to ensure me a 8192 cluster size for further expasion.
What I've noticed is that I have by now 2,5Gb of Non-Paged-Pool memory locked of my 16 Gb Ram installed!
Using poolmon.exe I found that the non paged pool is allocated to a proces with TAG "SpBu" that it seems to be related to StorageSpaces driver?!
It seems also that the more files I add to the SSpace the more non paged pool grows btw, if I free space from the SSpace the non paged pool decreases.
So, my question is:
Is it a normal behaviour that Storage Spaces needs to allocate so mouch memory (2,5Gb for 8,5Tb of data in parity mode) or I have some other problem maybe related to my additional Promise controller driver?
Andrea Bernacchini
View the full article