SUMMARY: vdump and Tru64 5.1B-2/PK 4

Bill Sadvary · *nix forums beginner Joined: 02 May 2003 Posts: 12

The fixed resulted in increasing the values for..

proc:
per_proc_data_size = 1342177280
max_per_proc_data_size = 10737418240
per_proc_stack_size = 33554432
max_per_proc_stack_size = 536870912

I had previously used the default values and the above is recommended
for our configuration.

I compared the pre-patch copy of sysconfigtab and the post-patch version
and there were no changes to proc subsystem values, so I guess there was a
change in the new vdump. ??

A thanks goes out to Kris Smith for referring me to a similar, previous
post converning dump (I was searching for vdump posts) and to Dr
Thomas.Blinn and John L. Lanier for leading me in the right direction.

-Bill Sadvary

---------- Forwarded message ----------
Date: Thu, 29 Jul 2004 15:08:08 -0400 (EDT)
From: Bill Sadvary <sadvary@dickinson.edu>
To: Tru64-UNIX-Managers <tru64-unix-managers@ornl.gov>
Subject: vdump and Tru64 5.1B-2/PK 4

After installing patch kit 4 on an ES40 running Tru64 5.1B-2, I am seeing
the following error when vdumping an AdvFS partition with 36 GB of usage.

vdump: Not enough memory to generate link table.

This worked fine up until the patch install.

I'm just doing a vdump of a cloneset, nothing fancy..

/sbin/vdump -0uf /dev/ntape/tape0_d1 /bck/coll_clone

The other ten or so smaller partitions get vdump'ed without a problem.

Any ideas?

Thanks,
-Bill

Google