01-16-2002
Perderabo,
I think the problem is my swap size. Because my machine ram is 128 MB swap is /dev/swap 1,41 389,120 389,120
swap definition is to big for Memory.
right ??
10 More Discussions You Might Find Interesting
1. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
2. SCO
Brief scenario of problem
working on contract for customer with supposedly identical setups in US and Europe
3 HP ML570 servers running SCO 5.07 networked together
servers 1 & 2 run the user applications , server 3 acts as backup / tape transport system between tape libraries
US side all... (0 Replies)
Discussion started by: ccarcher
0 Replies
3. Solaris
When ever i change my hard disk position from primary master to secondary slave, the solaris os gives a panic messge. how could i solve it. (2 Replies)
Discussion started by: ajay234
2 Replies
4. Solaris
Hi All, I've been troubleshooting this sendmail panic I'm getting on my dmesg. The errors are:
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: Losing ./qfl1G1hGuD000884: savemail panic
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: SYSERR(root): savemail: cannot save... (2 Replies)
Discussion started by: grumash
2 Replies
5. HP-UX
Hi all,
Does anybody know what kinds of events can prompt the following?
I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies
6. Solaris
Hello experts..
What is system panic? If a system is in that state.. what will happen?
Why is it goes to panic condition?
Just give me information about Panic condition.. How can i resolve this issue..?
If you know any links(URL) or Books...? replay me back....
Thanks in... (5 Replies)
Discussion started by: younus_syed
5 Replies
7. Solaris
Hi Guru's,
My Sun Fire v490 PRODUCTION server(Sol 5.9) has rebooted twice - on Apr'30 & May'08 2009.
And i found the following Error messages in /var/adm/messages file:
Apr 30 11:36:42 mumux201 unix:
Apr 30 11:36:42 mumux201 ^Mpanic/thread=2a1000c5d20:
Apr 30 11:36:42 mumux201 unix: ... (4 Replies)
Discussion started by: Hari_Ganesh
4 Replies
8. Solaris
Hi all,
solaris 10 system crashed, /var/adm/messages file:
panic/thread=3003ccaa060:
unix: mutex_exit: not owner, lp=60057340d28
owner=deadbeefdeadbee8 thread=3003ccaa06
0
unix:
genunix: 000002a10c4b1a00 sockfs:accept+1a8 (0, 3, 83,
5f03, 8c, 5c00)
genunix: %l0-3:... (1 Reply)
Discussion started by: Mehmet_Karaca
1 Replies
9. Solaris
Hi All,
I am getting the below error after login to box.
SunOS Release 5.10 Version Generic_147440-02 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
os-io Cross trap sync timeout: at cpu_sync.xword: 0x1010panic: failed to sto
p cpu8
panic: failed to... (1 Reply)
Discussion started by: chetansingh23
1 Replies
10. UNIX for Dummies Questions & Answers
Hi all,
I am running SCO6 in a VMWare environment. For the past two Sunday's during the system's automatic reboot I have received a Panic and the system has locked up. I have had to power off the VM and back on. I have never run into this sort of thing. Can someone help direct me to where... (1 Reply)
Discussion started by: Carlitos71
1 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)