11-25-2014
This is a kernel panic. It's not supposed to happen. You're probably not going to get a concrete answer unless it happens more than once in predictable circumstances.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies
2. Linux
Hi,
I have a three disk raid 5, with 500GB disks.
This is close to being full, and whilst I can just add another disk and rebuild to add another 500GB, I would prefer to replace with 1TB disks. So i have some questions.
Can I replace these disks one by one with bigger disks? I... (1 Reply)
Discussion started by: snoop2048
1 Replies
3. Virtualization and Cloud Computing
Hello Unix Community:
My task to figure out how to add a 20G volume to an existing EBS Array (RAID0) at AWS.
I haven't been told that growing the existing volumes isn't an option, or adding another larger volume to the existing array is the way to go. The client's existing data-store is... (0 Replies)
Discussion started by: Habitual
0 Replies
4. Emergency UNIX and Linux Support
Hi All
I have a RAID 5 array consisting of 4 drives that had a partial drive failure in one of the drives.
Rebooting shows the faulty drive as background rebuilding and mdadm /dev/ARRAYID shows three drives as in sync with the fourth drive as spare rebuilding.
However the array won't come... (9 Replies)
Discussion started by: Bashingaway
9 Replies
5. UNIX for Advanced & Expert Users
Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result?
cat /proc/mdstat
Personalities :
md126 : inactive sdb sdc sdd sde
1953536528 blocks super external:-md127/0
md127 : inactive sdd(S) sde(S) sdb(S) sdc(S)
9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies
6. UNIX for Advanced & Expert Users
Hi everyone,
I am not sure if I understand how mdadm --create /dev/md0 --level=container works?
A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device?
I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies
7. Red Hat
had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running..
created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda
trying to use mdadm to create RAID1 ..
I cannot even do it in "rescue" mode, I wonder if it can be done..
it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies
8. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I have been trying to create a USB RAID 5 using mdadm tool on Joli OS 1.2 (Ubuntu) but with no luck. I cannot even get pass the creation of array device (/dev/md0) and superblock. I am using 3 USB keys (2 16.4 GB kingston and 1 16GB sandisk).
My steps are:
... (5 Replies)
Discussion started by: powelltallen
5 Replies
10. UNIX for Advanced & Expert Users
Hi guys,
I'm new to RAID although I've had a server running raid5 for a while. It was delivered preinstalled like this and I never really wondered how to monitor and maintain it. This quick introduction just to let you understand why I'm such an idiot asking such a silly question.
Now what... (0 Replies)
Discussion started by: chebarbudo
0 Replies
LEARN ABOUT NETBSD
vpanic
PANIC(9) BSD Kernel Developer's Manual PANIC(9)
NAME
panic -- Bring down system on fatal error
SYNOPSIS
#include <sys/types.h>
#include <sys/systm.h>
void
vpanic(const char *fmt, va_list ap);
void
panic(const char *fmt, ...);
DESCRIPTION
The panic() and vpanic() functions terminate the NetBSD system. The message fmt is a printf(3) style format string which is printed to the
console and saved in the variable panicstr for later retrieval via core dump inspection. A newline character is added at the end automati-
cally, and is thus not needed in the format string.
If a kernel debugger is installed, control is passed to it after the message is printed. If the kernel debugger is ddb(4), control may be
passed to it, depending on the value of ddb.onpanic. See options(4) for more details on setting ddb.onpanic. If control is not passed
through to ddb(4), a ddb(4)-specific function is used to print the kernel stack trace, and then control returns to panic().
If control remains in panic(), an attempt is made to save an image of system memory on the configured dump device.
If during the process of handling the panic, panic() is called again (from the filesystem synchronization routines, for example), the system
is rebooted immediately without synchronizing any filesystems.
panic() is meant to be used in situations where something unexpected has happened and it is difficult to recover the system to a stable
state, or in situations where proceeding might make the things worse, leading to data corruption/loss. It is not meant to be used in scenar-
ios where the system could easily ignore and/or isolate the condition/subsystem and proceed.
In general developers should try to reduce the number of panic() calls in the kernel to improve stability.
RETURN VALUES
The panic() function does not return.
SEE ALSO
sysctl(3), ddb(4), ipkdb(4), options(4), savecore(8), swapctl(8), sysctl(8)
BSD
September 29, 2011 BSD