Operating System - HP-UX
1834136 Members
2235 Online
110064 Solutions
New Discussion

insufficient space on dump devices to save full scratch dump

 
delporte
Occasional Advisor

insufficient space on dump devices to save full scratch dump

Hello

Here is the message I do have when booting a C360 HP 10.20 :

"insufficient space on dump devices to save full scratch dump"

This must be a classical problem. I do understand that sotmething need to be
done on /stand

I need help :

- what need to be done now ?

- where can I find tutorial, similar posts, HP docs, ... to solve this
booting problem !

Thanks a lot

Marc

7 REPLIES 7
Steve Steel
Honored Contributor

Re: insufficient space on dump devices to save full scratch dump

Pete Randall
Outstanding Contributor

Re: insufficient space on dump devices to save full scratch dump

Marc,

This is, most likely, not a cause for concern. It is rare that a full crash dump is required for analysis and you can probably just ignore this message.


Pete

Pete
RAC_1
Honored Contributor

Re: insufficient space on dump devices to save full scratch dump

It has nothing to do with /stand. Which OS version?? lvlnboot -v. What is your dump device?? Seems that the space allocated to dump device is not enough. If you are primaru as dump device, how much has been configured?? Also check at file /etc/rc.config.d/crashconf. It gives few options to compresss the crash dump.

crashconf -v will also give you how much space is required to save the dump. You can configure new dump device with lvlnboot. The dump device has to be a contigeous.

lvcreate -L xxxM -C y /dev/vg00
lvlnboot -d /dev/vg00/lvolx

Once configured you can also save the crash dump with savecrash command.
man savecrash for details.

Anil
There is no substitute to HARDWORK
delporte
Occasional Advisor

Re: insufficient space on dump devices to save full scratch dump

Thanks for these replies

But, I not yet at this level in the boot process !

hpux is not loaded and the error message stops all actions

after main menu enter command : BOOT
interact Y

then ISL>

what can be done with ISL commands to go further ?

thanks

Marc
RAC_1
Honored Contributor

Re: insufficient space on dump devices to save full scratch dump

Fron ISL prompt,

hpux -is

Once you boot into single user mode, follow the commands that I gave you. If you do not have enough space for dump area, create it and reboot. Post if you have any problems.

Anil
There is no substitute to HARDWORK
delporte
Occasional Advisor

Re: insufficient space on dump devices to save full scratch dump

Thanks Anil for that reponse

From the ISL prompt, I've tried "single user" or "maintenance" mode :

hpux -is

hpux -lm boot

The result is still the same "insufficient space on dump devices to save full scratch dump" ...

so I do not have any prompt so I can't act and can't go further !

Marc
delporte
Occasional Advisor

Re: insufficient space on dump devices to save full scratch dump


To all

I do have the followings :

*************************************************************************

networking memory for fragment reassembly is restricted to 93224960 bytes

logical volume 64, 0X3 configured as root

logical volume 64, 0X2 configured as swap

logical volume 64, 0X2 configured as dump

swap device cable : (start & size given in ...

entry 0 - major is 64,minor is 0X2; start=0 size=1048576

warning : insufficient space on dump device to save full cratch dump

only 536870912 OS 1073742848 bytes would be save

starting the STREAMS daemons

memory information physical page size = 4096 bytes, logical page size = 4096
bytes

physical 1048473 Kytes, lockable : 783060 Kbytes, available : 900064 Bbytes

*************************************************************************

... then nothing, the station stops, no prompt !!!



When I do swtich off, I do have :

*************************************************************************

shutdown completed

It was not possible for the kernel to find a process that caused this cratch

warning : AUI loop back failed

system panic : HPUX B2352B HPUX (B10.20) #1: date

It was not possible for the kernel to find a process that caused this cratch

*************************************************************************

Regards

Marc