Sponsored Content
Operating Systems AIX AIX dump device not showing accurate size Post 303025893 by paqman on Wednesday 14th of November 2018 05:20:14 PM
Old 11-14-2018
AIX dump device not showing accurate size

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:
Mod Comment edit by bakunin: please use CODE-tags for data and terminal output too, thank you.

Last edited by bakunin; 11-15-2018 at 12:48 AM..
 

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.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies

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 Replies)
Discussion started by: ailnilanjan
3 Replies

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 Replies)
Discussion started by: click007
4 Replies

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... (2 Replies)
Discussion started by: DallasT
2 Replies

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... (0 Replies)
Discussion started by: capitalexall
0 Replies

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... (4 Replies)
Discussion started by: thecobra151
4 Replies

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... (1 Reply)
Discussion started by: newtoaixos
1 Replies

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: (1 Reply)
Discussion started by: reply.ravi
1 Replies

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... (3 Replies)
Discussion started by: cjashu
3 Replies

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... (2 Replies)
Discussion started by: solaris_1977
2 Replies
rdump(8c)																 rdump(8c)

Name
       rdump - file system dump across the network

Syntax
       /etc/rdump [ -key [ argument ... ] filesystem ]

Description
       The command copies to magnetic tapes, disks, or a dump image file all files changed after a certain date in the filesystem.  The command is
       identical in operation to except the f key must be specified and the file supplied should be of the following form:

       remote-system-name:device-or-file

       The command initiates a remote server, on the remote system to access the remote device or file.

Options
       With the command, you specify a string of one or more of the options described below.  If no options are specified, the key 9u is assumed.

       0-9     This number is the ``dump level.''  All files that were modified since the last date stored in  the  file  for  the  filesystem	at
	       lesser  levels  will be dumped.	If no date is determined by the level, the beginning of time is assumed.  Thus, the level 0 causes
	       the entire filesystem to be dumped, a level 5 is used for a weekly backup and a level 9 for a daily backup.

       B       The next argument is a number that specifies the size, in 1024-byte blocks, of a storage medium, such as a diskette or a  removable
	       disk.  See the first example.

       d       The  density  of  the  tape,  expressed in bits per inch, is taken from the next argument.  This density is used in calculating the
	       amount of tape used per reel.  The default density is 1600 bpi.

       f       Place the dump on the file or device specified by the next argument.  This file is specified as remote-system-name:device-or-file.

       n       Notify, by means similar to a command, all users in the group ``operator'' when needs operator attention.

       o       Provides compatibility with non-ULTRIX or pre-ULTRIX Version 2.0 remote systems.

       S       Displays amount of space used by without performing the dump operation.	This is used for presizing either for  file  preallocation
	       or to ensure the correct number of tapes or disks are on hand.

       s       The  next  argument  specifies  the  size of the dump tape (in feet).  When the specified size is reached, waits for the reel to be
	       changed.  The default tape size is 2300 feet.

       u       If the dump completes successfully, writes the date of the beginning of the dump to file This file records a separate date for each
	       filesystem  and	each  dump level.  The format of consists of one free format record per line: filesystem name, increment level and
	       format dump date.  The superuser can carefully edit to change any of the fields.

       W       The utility tells the operator what file systems need to be dumped.  This information is taken from the files and The option causes
	       to print out, for each file system in the most recent dump date and level, and highlights those file systems that should be dumped.
	       If the option is used, all other options are ignored, and exits immediately.

       w       Unlike lists only those filesystems that need to be dumped.

Examples
       This example reports number of bytes to be output for a level 0 dump of the root file system.  Please note: the file is not created.
       rdump OSf system:test /
       This example dumps the root(/) file system from the local system to a remote system named ``nihil''.  A level 0 dump to tape  is  performed
       and the file is updated.
       rdump 0uf nihil:/dev/rmt0h /

       This  example  dumps the user (/usr) file system from the local system to a remote system named ``dickens'' using the RX50 device named for
       output.	A level 0 dump is performed, but the file is not updated.
       rdump 0f dickens:/dev/rra1a /usr

       This example dumps the root file system to a non-ULTRIX or ULTRIX before Version 2.0 remote system.  A level 0 dump to a tape drive is per-
       formed and the file is updated.
       rdump 0ouf system:/dev/rmt0h /

       This  example  dumps the root file system to a non-ULTRIX or ULTRIX before Version 2.0 remote system.  A level 0 dump to the rx50 device is
       performed and the file is updated.  Note the specification of 400 as the device size in 1,024 byte blocks.
       rdump 0ouBf 400 system:/dev/rra1a /

       If you want to use / and you must have these entries in the file.

Diagnostics
       Same as with a few extra related to the network.

Files
       Required for user interface

See Also
       dump(8), rmt(8c)

																	 rdump(8c)
All times are GMT -4. The time now is 08:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy