Re: sysdump copy dir.
- From: Shawn Bierman <BiermanS@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 May 2006 12:16:50 -0500
Simon,
Thanks for your response but this doesn't answer my question. Why does
one node complain and the other doesn't when niether node has the space
to hold the dump.
-shawn
The best option is not to use a copy directory, but to have twoSimon.Green@xxxxxxxxxxxxx 5/24/06 10:37:55 AM >>>
dedicated
dump devices rather than using hd6.
We usually call ours hd7 and hd7a, (dump devices shouldn't be mirrored
so
these occupy the same locations on the two disks of a mirrored rootvg),
but
the name isn't important. (hd7 was the standard name for the dump
device in
older versions of AIX - v3, iirc.)
You can get the size of these using "sysdumpdev -e". However, you
should be
aware that this isn't always very accurate and the estimated size can
increase significantly over time as more use is made of the paging
spaces.
It is advisable to be generous in the allocation. The size can vary
considerable from one system to another, depending on the installed
software
and the nature of the applications on the server. If it's too small,
you'll
see errors to that effect in errpt. On my servers, it seems to range
from
around 200MB up to several GB!
The advantage of using hd7 and hd7a, (or whatever) is that the system
can be
booted immediately with no need to copy any data, but the dump remains
available when the system is up, (until the next crash). Now that
disks are
so much larger than they used to be space is not normally a problem. It
can
still be an issue if you've got an older server with relatively small -
e.g.
4.5GB - disks.
--
Simon Green
Altria ITSC Europe s.a.r.l.
AIX-L Archive at https://lists.princeton.edu/listserv/aix-l.html
New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf
Of
Shawn Bierman
Sent: 24 May 2006 15:16
To: aix-l@xxxxxxxxxxxxx
Subject: sysdump copy dir.
How big should the copy dir be for a system dump?
Currently I am receiving "The copy directory is too small." in error
report.
biermans@velma:/home/biermans > df -k /var/adm/ras
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd9var 81920 15164 82% 700 4% /var
biermans@velma:/home/biermans > sudo sysdumpdev -e
0453-041 Estimated dump size in bytes: 377487360
biermans@velma:/home/biermans > sudo sysdumpdev -l
primary /dev/hd6
secondary /dev/sysdumpnull
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression OFF
I have another node where the /var/adm/ras is smaller than the
sysdumpdev estimate and I do not receive these errors.
biermans@sf1n04en4:/home/biermans > df -k /var
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd9var 1048576 531960 50% 8837 4% /var
biermans@sf1n04en4:/home/biermans > sudo sysdumpdev -l
primary /dev/lg_dumplv
secondary /dev/sysdumpnull
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF
biermans@sf1n04en4:/home/biermans > sudo sysdumpdev -e
0453-041 Estimated dump size in bytes: 3768582144
Why do I get the error on one node and not the other? Clearly neither
filesystem will hold a dump of their estimated sizes (377M and 3.7G
respectivly)
-shawn
- Prev by Date: Re: sysdump copy dir.
- Next by Date: Re: sysdump copy dir.
- Previous by thread: Re: sysdump copy dir.
- Next by thread: Re: sysdump copy dir.
- Index(es):
Relevant Pages
|
|
