Dump and Savecore space
2007-12-24 20:38:00
------=_NextPart_000_00E1_01C12BE8.DCDC80D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I have a few questions with regard to crash dumps and save cores as it =
relates to various solaris versions (2.6 - 2.8)
1. With savecore, on solaris 2.7 and 2.8, it is possible to save only =
the kernel pages or you can save all memory pages. Is it possible to do =
the same thing on 2.6, or are only the kernel pages saved in 2.6.
2. Is there a formula available for determining the amount of space =
needed for crash dumps.=20
a.. For example, in solaris 2.7/2.8 if we decide to save only the =
kernel pages, and the server has 12GB of memory, then how much space =
should be set aside for the crash dump, how about 4GB, 8GB (formula or =
best practices would be great)=20
b.. If we save all the memory pages, then is it necessary to have a =
dump space of a full 12GB available, or do we also need to create space =
that includes any swap as well (so say potentially a 24GB dump space ?)=20
c.. Are there limits? (We are running a few E10K's, so the memory =
size can potentially grow to 64MB)
3. Are the limitations on where savecore saves the crash dump, ie can it =
be placed on a mounted NFS directory (not that we are going to do this, =
I am just looking for limitations) or can it be placed on a veritas =
parition (the default configuration here is root volumes are SDS, then =
all app/data are veritas.
4. Can solaris 2.6 specifically, but if there are limitations on other =
version I would like to know, write a dumpfile greater than 2GB (I am =
aware of, and have patched for the bug savecore doesn t work if swap =
slice is over 2G.)
Thanks, and I will summarize
-Tony
------=_NextPart_000_00E1_01C12BE8.DCDC80D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have a few questions with regard to =
crash dumps=20
and save cores as it relates to various solaris versions (2.6 -=20
2.8)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>1. With savecore, on solaris 2.7 and =
2.8, it is=20
possible to save only the kernel pages or you can save all memory pages. =
Is it=20
possible to do the same thing on 2.6, or are only the kernel pages saved =
in=20
2.6.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>2. Is there a formula available for =
determining the=20
amount of space needed for crash dumps. </FONT></DIV>
<UL dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<UL>
<LI><FONT face=3DArial size=3D2>For example, in solaris 2.7/2.8 if =
we decide to=20
save only the kernel pages, and the server has 12GB of memory, then =
how much=20
space should be set aside for the crash dump, how about 4GB, 8GB =
(formula or=20
best practices would be great)</FONT>=20
<LI><FONT face=3DArial size=3D2>If we save all the memory pages, =
then is it=20
necessary to have a dump space of a full 12GB available, or do we =
also need=20
to create space that includes any swap as well (so say potentially a =
24GB=20
dump space ?)</FONT>=20
<LI><FONT face=3DArial size=3D2>Are there limits? (We are running a =
few E10K's,=20
so the memory size can potentially grow to =
64MB)</FONT></LI></UL></UL>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>3. Are the limitations on =
where savecore=20
saves the crash dump, ie can it be placed on a mounted NFS directory =
(not that=20
we are going to do this, I am just looking for limitations) or can it be =
placed=20
on a veritas parition (the default configuration here is root volumes =
are SDS,=20
then all app/data are veritas.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV dir=3Dltr><FONT size=3D2><FONT face=3DArial>4. Can solaris 2.6 =
specifically, but=20
if there are limitations on other version I would like to know, write a =
dumpfile=20
greater than 2GB (I am aware of, and have patched for the bug savecore =
doesn t=20
work if swap slice is over 2G.)</FONT></FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT> </DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks, and I will =
summarize</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial =
size=3D2>-Tony</FONT></DIV></BODY></HTML>
------=_NextPart_000_00E1_01C12BE8.DCDC80D0--
Comments
Got something to say?
You must be logged in to post a comment.
