11-15-2018
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:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies
2. UNIX for Advanced & Expert Users
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 Replies)
Discussion started by: ailnilanjan
3 Replies
3. AIX
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 Replies)
Discussion started by: click007
4 Replies
4. Shell Programming and Scripting
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... (2 Replies)
Discussion started by: DallasT
2 Replies
5. Solaris
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... (0 Replies)
Discussion started by: capitalexall
0 Replies
6. AIX
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... (4 Replies)
Discussion started by: thecobra151
4 Replies
7. AIX
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... (1 Reply)
Discussion started by: newtoaixos
1 Replies
8. AIX
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: (1 Reply)
Discussion started by: reply.ravi
1 Replies
9. Solaris
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... (3 Replies)
Discussion started by: cjashu
3 Replies
10. Solaris
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... (2 Replies)
Discussion started by: solaris_1977
2 Replies
LVMDUMP(8) System Manager's Manual LVMDUMP(8)
NAME
lvmdump - create lvm2 information dumps for diagnostic purposes
SYNOPSIS
lvmdump [options] [-d directory]
DESCRIPTION
lvmdump is a tool to dump various information concerning LVM2. By default, it creates a tarball suitable for submission along with a prob-
lem report.
The content of the tarball is as follows:
- dmsetup info
- table of currently running processes
- recent entries from /var/log/messages (containing system messages)
- complete lvm configuration and cache
- list of device nodes present under /dev
- if enabled with -m, metadata dump will be also included
- if enabled with -a, debug output of vgscan, pvscan and list of all available volume groups, physical volumes and logical volumes will be
included
- if enabled with -c, cluster status info
OPTIONS
-h -- print help message
-a -- advanced collection
WARNING: if lvm is already hung, then this script may hang as well if -a is used
-m -- gather LVM metadata from the PVs
This option generates a 1:1 dump of the metadata area from all PVs visible to the system, which can cause the dump to increase in
size considerably. However, the metadata dump may represent a valuable diagnostic resource.
-d directory -- dump into a directory instead of tarball
By default, lvmdump will produce a single compressed tarball containing all the information. Using this option, it can be instructed
to only produce the raw dump tree, rooted in directory.
-c -- if clvmd is running, gather cluster data as well
ENVIRONMENT VARIABLES
LVM_BINARY
The LVM2 binary to use. Defaults to "lvm". Sometimes you might need to set this to "/sbin/lvm.static", for example.
DMSETUP_BINARY
The dmsetup binary to use. Defaults to "dmsetup".
Red Hat, Inc. LVM TOOLS 2.02.67(2) (2010-06-04) LVMDUMP(8)