Virtual Partition Dump Files | HP-UX Virtual Partitions

	HP-UX Virtual Partitions By Marty Poniatowski
	Table of Contents

	Chapter 2. Working With vPars

When a Virtual Partition crashes, a dump file is created in /stand/vmpon.dmp. When the Virtual Partition boots, files are created in /var/adm/crash/vpar. The files have an extension with a number indicating the number of the dump that occurred. For instance, vpmon.1, vpmon.dmp.1, and summary.1 indicate the first set of files that are saved in /var/adm/crash/vpar.

An example of what you might see in /stand and /var/adm/crash/vpar related to dumps are shown in the following listing:

 VPARNAME = extraq1  # ll /stand  total 100400  -rw-r--r--  1 root     sys          19 Jul 13 15:04 bootconf  drwxr-xr-x  4 root     sys        2048 Oct 18 11:43 build  drwxrwxrwx  5 root     sys        1024 Oct 18 13:06 dlkm  drwxrwxrwx  5 root     root       1024 Oct 18 11:21 dlkm.vmunix.prev  -rw-r--r--  1 root     sys        3388 Oct 18 13:16 ioconfig  -r--r--r--  1 root     sys          82 Jul 13 15:34 kernrel  drwxr-xr-x  2 root     sys        1024 Oct 18 13:18 krs   drwxr-xr-x  2 root       root        1024 Oct 18 13:16 krs_lkg  drwxr-xr-x  2 root       root        1024 Oct 18 13:18 krs_tmp  drwxr-xr-x  2 root       root        8192 Jul 13 15:04 lost+found  -rw-------  1 root       root          12 Oct 18 13:16 rootconf  -r--r--r--  1 root       sys         2035 Oct 18 11:42 system  -r--r--r--  1 root       sys          994 Jul 13 15:28 system.01  -r--r--r--  1 root       sys          999 Jul 13 15:56 system.02  -r--r--r--  1 root       sys          994 Jul 13 15:28 system.base  drwxr-xr-x  2 root       sys         1024 Jul 13 15:37 system.d  -r--r--r--  1 root       sys         2035 Oct 18 10:55 system.prev  -rwxr-xr-x  1 root       root     22682568 Oct 18 13:16 vmunix  -rwxr-xr-x  1 root       root     22682568 Oct 18 11:04 vmunix.prev  -rw-------  1 root       sys         8232 Oct 18 13:36 vpdb  -rw-------  1 root       root        8232 Jul 17 14:11 vpdb.OLD  -r-xr-xr-x  1 bin        bin       837616 Aug 31 18:59 vpmon  -rw-------  1 root       root    5078504 Oct 10 10:43 vpmon.dmp <-- vPar dump  # ll /var/adm/crash/vpar                               <-- vPar dump directory  total 46464  -rw-r--r--  1 root       root          2 Oct 43 count  -rw-r--r--  1 root       root      16794 Jul 17 13:26 summary.0  -rw-r--r--  1 root       root      17953 Jul 18 10:35 summary.1  -rw-r--r--  1 root       root      19538 Jul 36 summary.2  -rw-r--r--  1 root       root      10012 Oct 43 summary.3  -r-xr-xr-x  1 root       root     855928 Jul 17 13:26 vpmon.0  -r-xr-xr-x  1 root       root     855928 Jul 18 10:35 vpmon.1  -r-xr-xr-x  1 root       root     855928 Jul 18 11:36 vpmon.2  -r-xr-xr-x  1 root       root     837616 Oct 10 10:43 vpmon.3  -rw-------  1 root       root    5078504 Jul 17 13:26 vpmon.dmp.0  -rw-------  1 root       root    5078504 Jul 18 10:35 vpmon.dmp.1  -rw-------  1 root       root    5078504 Jul 18 11:36 vpmon.dmp.2  -rw-------  1 root       root    5078504 Oct 10 10:43 vpmon.dmp.3

The /var/adm/crash/vpar directory has in it the vPar dump-related files for four (0-3) crashes.

The dump file created in /stand is saved in /var/adm/crash/vpar and and extended with the crash number. The dump file in /stand is overwritten with each crash, but you have a history with all of the dump files and related information in /var/adm/crash/vpar. Please leave in place the /stand/ vpmon.dmp file.

Top