|
|
| Fredrik 2004-09-28, 8:28 am |
| On a newly upgraded system from 5.1A pk6 to 5.1B pk4 there seems to be
a change in vdump. It consumes huge amounts of memory on big filesets.
This error came: vdump: Not enough memory to generate link table.
After setting the process limit to 500 mb everything was fine, the
process consumes about 450 mb memory.
But a dump on 5.1A on the same fileset consumes only a couple of mb.
It seems like a bug or???
| |
| Stephen Carpenter 2004-10-15, 9:28 pm |
| There will be an ERP soon to correct this problem. As a workaround you
can use the PK3 (or V5.1A PK6) version of vdump.
Regards,
Stephen.
Fredrik wrote:
> On a newly upgraded system from 5.1A pk6 to 5.1B pk4 there seems to be
> a change in vdump. It consumes huge amounts of memory on big filesets.
> This error came: vdump: Not enough memory to generate link table.
> After setting the process limit to 500 mb everything was fine, the
> process consumes about 450 mb memory.
> But a dump on 5.1A on the same fileset consumes only a couple of mb.
>
> It seems like a bug or???
| |
| Leo Mayerhofer 2004-10-15, 9:28 pm |
|
An advise concerning increased memory usage of vdump
could be found in
http://h30097.www3.hp.com/unix/erp/BU040831_EW01.html
Regards,
Leo Mayerhofer
Stephen Carpenter wrote:[vbcol=seagreen]
>
> There will be an ERP soon to correct this problem. As a workaround you
> can use the PK3 (or V5.1A PK6) version of vdump.
>
> Regards,
>
> Stephen.
>
> Fredrik wrote:
| |
| Christoffer Hjortlund Heder 2004-11-03, 5:52 pm |
| Fredrik wrote:
> On a newly upgraded system from 5.1A pk6 to 5.1B pk4 there seems to be
> a change in vdump. It consumes huge amounts of memory on big filesets.
> This error came: vdump: Not enough memory to generate link table.
> After setting the process limit to 500 mb everything was fine, the
> process consumes about 450 mb memory.
> But a dump on 5.1A on the same fileset consumes only a couple of mb.
>
> It seems like a bug or???
Yes... It do indeed...
|
|
|
|