Solved

The largest dump device is too small

Posted on 2014-01-13
11
757 Views
Last Modified: 2014-01-22
I am getting error about dmpchk_toosmall E87EF1BE.

Probable Causes
Neither dump device is large enough to accommodate a system dump at this time.

        Recommended Actions
        Increase the size of one or both dump devices.

Detail Data
Largest dump device
lgdumplv
Largest dump device size in kb
     550xxxx
Current estimated dump size in kb
     576xxxx

In this case if I need to increase dump device size, what is the proper procedure to dump device size in mirrored rootvg.

Thanks.
0
Comment
Question by:sams20
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39777261
Hi,

(1) Determine your dump devices:

sysdumpdev -l

You might see something like this:
primary              /dev/lgdumplv
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON

Open in new window

sysdumpnull is a dummy device, I only assume it as the secondary device.
If the secondary device is a real device use the name you found with the command given above to repeat all the commands given below (except (3)) for that device!

(2) Check the device sizes

lslv lgdumplv

Take the value shown next to "LPs" on the left and multiply it with the value next to "PP Size" on the right to get the device size in MB. Note the value for "PP Size". You will neeed it in (5) below.

(3) Check the size required to accommodate a dump:

sysdumpdev -e | awk '{printf "%.0f\n", $NF /1024/1024}'

This will show the estimated dump size in MB.

(4) Compute the difference between the values obtained in (2) and (3).

(5) Divide the value found in (4) by the "PP Size" found in (2). Round up to the next integer. This is the number of required additional partitions. I'll call it "nn" below.

(6) Increase the size of the device(s)

extendlv lgdumplv nn

That's all. The change will take effect on both sides of the mirror, and there is no background process which must be restarted.

(Optional) Check for success:

/usr/lib/ras/dumpcheck -p

If you don't get any output everything is fine now.
0
 

Author Comment

by:sams20
ID: 39777401
I got,

1)
# sysdumpdev -l
primary              /dev/lgdumplv
secondary            /dev/sysdumpnull
copy directory       /xxxx_dump
forced copy flag     FALSE
always allow dump    TRUE
dump compression     ON
type of dump         traditional

2)
#lslv lgdumplv
PP SIZE:        256 megabyte(s)

LPs: 21

21LPs size: 5376MB

PPs: 42.

3)
I don't know which one should be correct,

# sysdumpdev -e | awk '{printf"%.of\n",$NF /1024/1024}'
13000f
OR
# sysdumpdev -e | awk '{print "%.of\n",$NF /1024/1024}'
%.of
 5632.8
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39777425
sysdumpdev -e | awk '{printf "%.0f\n", $NF /1024/1024}'

"0" in "%.0f\n" is the digit  zero, not the letter "o".
0
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

 

Author Comment

by:sams20
ID: 39777481
from, sysdumpdev -e | awk '{printf "%.0f\n", $NF /1024/1024}'
I got 5633 MB

4) Difference, 257MB

5) Devided by PPs ---> 6.1
Then here, nn = 6.1
0
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 39777504
You must divide by "PP Size", as I wrote in (5), not by "PPs".

257  divided by 256 rounded up to the next integer gives 2.

So "nn" is "2" and the command to extend the dump device is

extendlv lgdumplv 2

We're almost there ...
0
 

Author Comment

by:sams20
ID: 39777566
Now I understand, but I have a question here, if I extend lgdumplv on one hdisk, what abaout another hdisk. It looks like mirrored rootvg, there are two hdisks in the rootvg.
# lsvg -p rootvg
hdisk0            active            536         396        
hdisk1            active            536         396
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39777574
Dump devices are generally not mirrored.

Check with

lslv -l lgdumplv

Do you see both disks?

If so (which I doubt) there is no reason to get worried nonetheless. Changing an LV always takes effect on both sides of the mirror.
0
 

Author Comment

by:sams20
ID: 39779243
With this command, "lslv -l lgdumplv" I got both hdisks.
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39779372
So your dump device is mirrored which is quite uncommon, indeed.

So run

extendlv lgdumplv 2

and the dump LV will be extended by 2 LPs (logical partitions) which means that both copies of the LV will be extended by 2 PPs (physical partitions) each.

lsvg -p rootvg will then show

hdisk0            active            536         394        
hdisk1            active            536         394

Don't worry, LVM will take care of all this, there is no other command required than just extendlv.
0
 

Author Comment

by:sams20
ID: 39783129
If I extend lgdumplv with more than 2PPs like 3 or 4 PPs, will it work.
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39783252
Yes, why not? There is sufficient space in rootvg anyway.

Do you want to make provisions for future growth of your crash dumps?
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
FreeBSD on EC2 FreeBSD (https://www.freebsd.org) is a robust Unix-like operating system that has been around for many years. FreeBSD is available on Amazon EC2 through Amazon Machine Images (AMIs) provided by FreeBSD developer and security office…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question