10-26-2007
following :
sysdumpdev -l # to list dump device
sysdumpdev -L # to list last time system dumped
sysdumpdev -e # to estimate the size of a dump under current loading
Largest dump device size in kb ***
This is the size of the dump device.
Current estimated dump size in kb ***
And this is the estimated size of the dump in kb if you system were to crash under your current load.
You just need to :
extendlv lg_dumplv NUM_PPS (example lg_dumplv is your dump lv )
make your dumplv large enough to fit your needs ....
good luck ...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. 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
3. Shell Programming and Scripting
I have two text files like this:
file1.txt:
133 10
133 22
133 13
133 56
133 78
133 98
file2.txt:
158 38
158 67
158 94
158 17
158 23
I'm basically trying to have awk check the second largest value of the second column of each text file, and cat it to its own text file. There... (13 Replies)
Discussion started by: theawknewbie
13 Replies
4. 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
5. 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
6. 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
7. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
8. Solaris
I've never seen this, is it normal for 11.2? Anyway to change it back to dumping metadata or is this simply an overly verbose message I may ignore?
kernel without ZFS metadata (4 Replies)
Discussion started by: LittleLebowski
4 Replies
9. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
10. AIX
I am trying to configure dump devices on my AIX server. Running 7100-03-04-1441. My dump device needs to be about 2GB in size. My PP Size is 1024MB, so I create the device with 2 PPs. When I run lslv on the dump device, it shows the 2 PPs, and a PP Size of 1024 megabytes. However, a dumpcheck... (4 Replies)
Discussion started by: paqman
4 Replies
cr_open(3) Library Functions Manual cr_open(3)
NAME
cr_open() - open crash dump for reading
SYNOPSIS
DESCRIPTION
The library call opens a crash dump and passes back a crash dump descriptor.
The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length.
The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash
dump.
flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines for this
crash dump, except for cr_verify(3), which has its own flags parameter.
The library will not attempt to verify checksums of files in the crash
dump if this flag is set.
The library will write messages to stderr during time-consuming operations
(decompressions and checksums) if this flag is set.
RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5).
EXAMPLES
The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash
dump see the cr_read(3) manual entry.
AUTHOR
was developed by HP.
SEE ALSO
cr_close(3), cr_perror(3), libcrash(5).
cr_open(3)