AIX dump device not showing accurate size Post: 303025928

Sponsored Content

Operating Systems AIX AIX dump device not showing accurate size Post 303025928 by paqman on Thursday 15th of November 2018 10:22:29 AM

11-15-2018

Registered User

Quote:

Originally Posted by bakunin

Just because you create a logical volume of type "dump" doesn't mean it is used as dump. Use the sysdumpdev to find out which dump device is actually in use. You can also use this command to find out how big the dump device has to be (-e, estimate) and to set the dump device (-Pp <device>).

On another note, you seem to have doctored with the rootvg because it is quite unusual to have a 1GB PP-size. Usual PP-sizes in rootvgs are indeed 64MB and 128MB. I don't know what exactly you did, but: might it be that this has something to do with it?

I hope this helps.

bakunin

I figured out the problem. Yes I had already used sysdumpdev to verify that I was actually using the devices in question. The rootvg is fine, the reason it has a 1GB PP size is because the disks it was installed on are 4TB disks. So I believe it defaulted to 1GB PP size.

The problem was with the dumpcheck script. I ran it with debug on and found that it was reporting the block size for the dump device as 512 bytes. When I knew in fact that the block size was 4k. I found that it was an old version from 2010 that was missing a lot that the version on on most of our other servers were using. I copied the later version of the script, which correctly specified the block size of the dump device, and voila. So really, the dump device was fine, just the dumpcheck script was reporting the wrong size.

Thanks for your reply!

This User Gave Thanks to paqman For This Post:

paqman

View Public Profile for paqman

Find all posts by paqman

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

core dump file size

Hi All, is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally? Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes....

2. UNIX for Advanced & Expert Users

Showing Device Does Not Exist While Taking Backup

Friends, while taking backup on /dev/rmt/0cn it is showing device does not exists. I have checked /dev/rmt 0cn is present there with link file created in /devices/pci@8,700000/scsi@5/st@5,0:cn I have checked cd /devices/pci@8,700000/scsi@5 but st@5,0:cn is not there. But I found st@3,0:cn. ...

3. AIX

The largest dump device is too small

1.what is dump device in AIX?... 2. i m getting this error message The largest dump device is too small. when i check the paging space , it is used only 41% any help welcome

4. Shell Programming and Scripting

Shell Script not showing accurate Time Stamp and Size

Hey guys - I have made this script and for some reason, I dont see time stamp as "Month-Day-YYYY Hours-Mins" - all i see is Month and Day. Also, my file size is approximated. For example, if the size is 19,606KB - the script shows as 20M. Is there a way to see the exact file size? How do i...

5. Solaris

iSCSI disk showing incorrect size

Hi, I have a very frustrating issue! I hope you guys can assist When a disk is presented out the iSCSI target display a lower disk capacity SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31 ISCSI Patch 119090-31, 141878-11 Unix Commands To discover Target bash-3.00# i...

6. AIX

The largest dump device is too small.

E87EF1BE 0605150011 P O dumpcheck The largest dump device is too small. bash-3.00$ errpt -aj E87EF1BE | more --------------------------------------------------------------------------- LABEL: DMPCHK_TOOSMALL IDENTIFIER: E87EF1BE Date/Time: Sun Jun 5 15:00:01...

7. AIX

change the primary dump device of a vio server

Hi how to change the primary dump device in a vio server ? $ ioslevel 2.2.0.11-FP-24 SP-01 $ oem_setup_env # sysdumpdev -l primary /dev/sysdumpnull secondary /dev/hd6 copy directory /var/adm/ras forced copy flag TRUE always allow dump TRUE dump...

8. AIX

Dump device

Hi all I have a query about dump device in aix, i asked this question on interview. what is dump device, how to add dump device & its work. kindly give this answer, thanks in advance. :confused:

9. Solaris

dedicated crash dump device

Hello Guys, I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to : 1) create a mount point? 2) add entry in /etc/vfstab? 3) is this slice wu or wm? 4) should...

10. Solaris

Showing strange size in df output

Hi, This is Solaris-10 box and in few of file-system (root file-system of non global zones), usage/available is not showing correct size. I am not able to figure out, what is eating up this space. Global Server - bdrpod01 Non Global zone - bdrpod01-zputq01 root@bdrpod01:/root# df -h...

LEARN ABOUT OSF1

expand_dump

expand_dump(8)						      System Manager's Manual						    expand_dump(8)

NAME

       expand_dump - Produces a non-compressed kernel crash dump file

SYNOPSIS

       /usr/sbin/expand_dump input-file output-file

DESCRIPTION

       By  default, kernel crash dump files (vmzcore.#) are compressed during the crash dump.  Compressed core files can be examined by the latest
       versions of debugging tools that have been recompiled to support compressed crash dump files.  However, not  all  debugging  tools  may	be
       upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool.  The expand_dump
       utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files.  This  non-compressed
       version can also be read by any upgraded tool.

       This  utility  can  only  be used with compressed crash dump files, and does not support any other form of compressed file.  You cannot use
       other decompression tools such as compress, gzip, or zip on a compressed crash dump file.

       Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of	up
       to  60:1.  Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests
       by halting your system and forcing a crash as described in the Kernel Debugging manual.	Use an upgraded debugger to determine the value of
       the  variable  dumpsize.   Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump.
       Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task.

RETURN VALUES

       Successful completion of the decompression.  The user did not supply the correct number of command line arguments.  The	input  file  could
       not  be	read.	The  input file is not a compressed dump, or is corrupted.  The output file could not be created or opened for writing and
       truncated.  There was some problem writing to the output file (probably a full disk).  The input file is not formated consistantly.  It	is
       probably corrupted.  The input file could not be correctly decompressed.  It is probably corrupted.

EXAMPLES

       expand_dump vmzcore.4 vmcore.4

SEE ALSO

       Commands: dbx(1), kdbx(8), ladebug(1), savecore(8)

       Kernel Debugging

       System Administration

																    expand_dump(8)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

core dump file size

Discussion started by: pushp.gahlot

2. UNIX for Advanced & Expert Users

Showing Device Does Not Exist While Taking Backup

Discussion started by: ailnilanjan

3. AIX

The largest dump device is too small

Discussion started by: click007

4. Shell Programming and Scripting

Shell Script not showing accurate Time Stamp and Size

Discussion started by: DallasT