SOLVED
Are you up to date on patching? I can see mention of an error similar to this in some of the VM cumulative patches - latest is PHKL_42850 - might want to ensure you have that and dependencies?
A Memory Resource Group is a function of PRM, but I suspect that PRM may still do some work kernel-side even when you aren't using it - nevertheless it would be interesting to see the output of "prmconfig" - I think its likely you will just get back "Cannot display configuration. PRM is not configured. (PRM-226)", but you never know...
FInaly - the message about not growing a memory space is perfectly legal in some cirumstances, particularly if you are under memory pressure - are you sure you weren't _increasing_ filecache_min ? Maybe it was laready set lower than 5% ?? The output of "kctune -v filecache_max filecache_min" would tell us (it would be useful to know how much physical memory you have as well - "machinfo" should tell you that
I am an HPE Employee
Physical memory = 522455 31.9g
So you have about 52GB of memory on this system - 10% would be 5.2GB, 5% would be 2.6GB.
Tunable filecache_max Description Maximum amount of physical memory to be used for caching file I/O data Module fs_bufcache Current Value 134217728 Value at Next Boot (auto) [10%] Value at Last Boot 134217728 Default Value 17067343872 (automatic) Can Change Immediately (Automatic Tuning Disabled) Tunable filecache_min Description Minimum guaranteed physical memory used for caching file I/O data Module fs_bufcache Current Value 134217728
So filecache_max and filecache_min are both currently set to 134217728 (134217728 / 1024 / 1024 = 128MB)
If filecache_min and filecache_max were set to 128MB and you tried to change them to 2.6GB and 5.2GB respectively when there was significant memory pressure, I suspect the system was doing the right thing when it told you " Failed to resize up (grow) the Filedata Memory Resource Group".
Dennis,
> >The output of "kctune -v filecache_max filecache_min" would tell us
>
> Aren't they the "now" values of: 134,217,728
Yes, they are... I'm one of those people who shouts to my wife "have you seen the car keys" when they are right in front of me!
I am an HPE Employee
Which version of 11.31 are you running and which version of HPVM? My guess is you're running the March 2012 or later Fusion and HPVM v6.1 or later.
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Dennis,
> >So you have about 52 GB of memory on this system - 10% would be 5.2 GB, 5% would be 2.6 GB.
>
> Huh? I see 32GB and 522,455 pages of 64 KB each.
I was reading this from the OP's kmeminfo output:
>> Physical memory = 522455 31.9g 100%
Is that wrong?
I am an HPE Employee
@Duncan Edmonstone wrote:I was reading this from the OP's kmeminfo output:
>> Physical memory = 522455 31.9g 100%
Is that wrong?
Hi Duncan,
The kmeminfo output displays the physical memory in three formats - number of pages, bytes, percent. Looking at his output:
Physical memory usage summary (in page/byte/percent):
Physical memory = 522455 31.9g 100%
There are 522455 memory pages, 32GB of RAM in the system. That being the case, we know that the system is using 64K memory pages (32 * 1024 * 1024) = 33,554,432 bytes / 522,455 pages = 64. This makes sense on an Integrity VM host because we automatically tune the base_pagesize=64 on systems configured as VM Hosts or VSPs.
My guess is this system is running March 2012 release or newer and Integrity VM v6.1 or newer because at that release we automatically grab 92% of the available memory when HPVM starts and assign it to the HPVM/vPar memory pool. This is expected behavior that is documented in the Integrity VM/vPars v6.1 Admin Guide.
Hope this helps,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
hmmm - it would appear I have lost the ability to read! Not sure how I was reading that as 52GB???
I am an HPE Employee
