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 -p shows that my dump device is only 256MB in size. dumpcheck seems to think my PP Size is only 128MB. Here you can see the output of lslv dump2lv showing the PP Size and PPs:
Code:
LOGICAL VOLUME: dump2lv VOLUME GROUP: rootvg
LV IDENTIFIER: 00c1077000004b0000000166fa6a2f10.11 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 1024 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 2 PPs: 2
STALE PPs: 0 BB POLICY: non-relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 8
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
INFINITE RETRY: no PREFERRED READ: 0
And here you can see dumpcheck showing the size being only 262144 kb:
Code:
# /usr/lib/ras/dumpcheck -p
The largest dump device is too small.
Largest dump device
dump2lv
Largest dump device size in kb
262144
Current estimated dump size in kb
1955880
My rootvg does show that the size used is indeed 2GB. So where is this extra space going, and why is dumpcheck not reporting all the size for my dump device?
Thanks in advance!
Moderator's Comments:
edit by bakunin: please use CODE-tags for data and terminal output too, thank you.
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT V7
dump
DUMP(1M)DUMP(1M)NAME
dump - incremental file system dump
SYNOPSIS
dump [ key [ argument ... ] filesystem ]
DESCRIPTION
Dump copies to magnetic tape all files changed after a certain date in the filesystem. The key specifies the date and other options about
the dump. Key consists of characters from the set 0123456789fusd.
f Place the dump on the next argument file instead of the tape.
u If the dump completes successfully, write the date of the beginning of the dump on file `/etc/ddate'. This file records a separate
date for each filesystem and each dump level.
0-9 This number is the `dump level'. All files modified since the last date stored in the file `/etc/ddate' for the same filesystem at
lesser levels will be dumped. If no date is determined by the level, the beginning of time is assumed; thus the option 0 causes the
entire filesystem to be dumped.
s The size of the dump tape is specified in feet. The number of feet is taken from the next argument. When the specified size is
reached, the dump will wait for reels to be changed. The default size is 2300 feet.
d The density of the tape, expressed in BPI, is taken from the next argument. This is used in calculating the amount of tape used per
write. The default is 1600.
If no arguments are given, the key is assumed to be 9u and a default file system is dumped to the default tape.
Now a short suggestion on how perform dumps. Start with a full level 0 dump
dump 0u
Next, periodic level 9 dumps should be made on an exponential progression of tapes. (Sometimes called Tower of Hanoi - 1 2 1 3 1 2 1 4 ...
tape 1 used every other time, tape 2 used every fourth, tape 3 used every eighth, etc.)
dump 9u
When the level 9 incremental approaches a full tape (about 78000 blocks at 1600 BPI blocked 20), a level 1 dump should be made.
dump 1u
After this, the exponential series should progress as uninterrupted. These level 9 dumps are based on the level 1 dump which is based on
the level 0 full dump. This progression of levels of dump can be carried as far as desired.
FILES
default filesystem and tape vary with installation.
/etc/ddate: record dump dates of filesystem/level.
SEE ALSO restor(1), dump(5), dumpdir(1)DIAGNOSTICS
If the dump requires more than one tape, it will ask you to change tapes. Reply with a new-line when this has been done.
BUGS
Sizes are based on 1600 BPI blocked tape. The raw magtape device has to be used to approach these densities. Read errors on the filesys-
tem are ignored. Write errors on the magtape are usually fatal.
DUMP(1M)
11-14-2018
