Sponsored Content
Operating Systems Solaris BAD TRAP: type=30 rp=2a10001b840 addr=2a000012040 mmu_fsr=0 Post 95276 by fangfang on Monday 9th of January 2006 11:45:08 PM
Old 01-10-2006
Thanks alot for your comments. I will come to Sun for further analysis.

The reason that I suspect HW is, there are 18 Solaris nodes in my system, they are exactly same in plateform/HW/OS/App(auto installed by DHCP script), only this node corrupted 4 times in 20 days with same reason(a little differ of addr). I thought high work load might crash the scheduler but it seems not true because the 18 nodes are configured in load balance...

Anyway, see what answer from Sun. Thanks again.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

k_trap - kernel mode trap type 0x0000000E

HELP is urgently required, I run on SCO Unix 3 and this is the panic message that I get every time that I reboot 10U k_trap - kernel mode trap type 0x0000000E I have checked the swap already having the following results: #swap -l path dev swaplo blocks free... (3 Replies)
Discussion started by: alex_slb
3 Replies

2. UNIX for Dummies Questions & Answers

bad trap & continuous reboot

I have a system that upon boot, will declare a bad trap and reboot, whereupon it encounters the same bad trap and reboots in an endless cycle until I stop it. I can get to the ok prompt. An attempt to boot in single user mode left the box completely hung and required a power cycle to re-establish... (3 Replies)
Discussion started by: forbin24
3 Replies

3. UNIX for Dummies Questions & Answers

finger, getting name and pts from ip addr

im ultra new at unix and was wondering if its possible to create aliases of the write command that send messeges to users using an ip address. i was thinking to use the '|awk' with the command finger but as i've said im a total newbie. thanks a lot in advance. (2 Replies)
Discussion started by: swag:þ
2 Replies

4. AIX

AIX 5.3 , gensyms command, translate 32 bit addr to 64 bit addr

I am trying to map the information from the gensyms command, Its gives information about the various symbols info like symbol type, addr offset, and the main libraries addr starting point. My problem is , how do I map this 32 bit addr to a 64 bit addr, I am trying to extract Segment # information... (0 Replies)
Discussion started by: mrmeswani
0 Replies

5. Solaris

Panic BAD TRAP errors

One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly? Thanks Margaret Floyd Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies

6. Shell Programming and Scripting

Cntl+z Trap is not detecting ??? Help required to add a trap detection ???

Hi folks, I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:.... The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies

7. SCO

PANIC: k_trap - Kernel mode trap type 0x0000000E

Hi, i'm another question: I'm a directory /usr/data on my server sco unix 5.0.5: # du /usr/data 4386948 /usr/data I'm tried to connect to ftp directory /usr/data to this server and: PANIC: k_trap - Kernel mode trap type 0x0000000E Cannot dump 262040 pages to dumpdev hd(1/41):space... (3 Replies)
Discussion started by: sebpes
3 Replies

8. IP Networking

TTL for IP addr from DNS through C code

Hi All, I know that getaddrinfo() return the multiple IP addresses (if present) for a hostname. But, I want to know how to get the TTL value for this list from DNS. I want to get this TTL value and cache this IP address list for that much time and then again go for DNS resolution if TTL expires. ... (2 Replies)
Discussion started by: softindia
2 Replies

9. Shell Programming and Scripting

Record the Signal Type or Number in Bash Trap function

In my Bash script I have an exit/cleanup function in a trap statement like: trap exitCleanup 1 2 3 6 15 25 Is there anyway to capture which signal # has occurred to record in a log file. Please note I am trying to avoid something like: trap 'mySignal=1; exitCleanup' 1 trap... (1 Reply)
Discussion started by: ckmehta
1 Replies

10. Homework & Coursework Questions

VM trap may work differently than a pure install trap.

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: That is the last reply I received from my instructor, and I'm looking for some alternatives. When using... (2 Replies)
Discussion started by: newuser45
2 Replies
scconf_dg_vxvm(1M)					  System Administration Commands					scconf_dg_vxvm(1M)

NAME
scconf_dg_vxvm - add, change, or update VxVM device group configuration. SYNOPSIS
scconf -a -D type=vxvm,devicegroup-options[,localonly=true|false] scconf -c -D devicegroup-options[,sync] scconf -r -D name=devicegroupname DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_vxvm command is used to add, change, and remove the VERITAS Volume Manager (VxVM) device groups to the Sun Cluster device- groups configuration. OPTIONS
See the scconf(1M) man page for the list of supported generic device-group options. The following action options describe the actions that the command performs. Only one action option is allowed in the command. -a Add a VxVM device group to the cluster configuration. The -a (add) option adds a new VxVM device group to the Sun Cluster device-groups configuration. With this option you define a name for the new device group, specify the nodes on which this group can be accessed, and specify a set of properties used to control actions. For VxVM device groups, you can only assign one VxVM disk group to a device group, and the device-group name must always match the name of the VxVM disk group. You cannot create a VxVM device group unless you first import the corresponding VxVM disk group on one of the nodes in that device's node list. Before you can add a node to a VxVM device group, every physical disk in the disk group must be physically ported to that node. After you register the disk group as a VxVM device group, you must first deport the disk group from the current node owner and turn off the auto-import flag for the disk group. To create a VxVM device group for a disk group, you must run the scconf command from the same node where the disk group was created. -c Change the ordering of the node preference list, change preference and failback policy, and change the desired number of sec- ondaries. The scconf -c (change) option changes the order of the potential primary node preference, to enable or disable failback, to add more global devices to the device group, and to change the desired number of secondaries. The sync suboption is used to synchronize the clustering software with VxVM disk-group volume information. The sync suboption is only valid with the change form of the command. Use the sync suboption whenever you add or remove a VxVM volume from a VxVM device group or change any volume attribute, such as owner, group, or access permissions. Also use the sync suboption to change a device-group configuration to a replicated or non-replicated configuration. For device groups that contain disks that use Hitachi TrueCopy data replication, this sync suboption synchronizes the device- group configuration and the replication configuration. This synchronization makes Sun Cluster software aware of disks that are configured for data replication and enables the software to handle failover or switchover as necessary. After you create a Solaris Volume Manager disk set that contain disks that are configured for replication, you must run the sync suboption for the corresponding svm or sds device group. A Solaris Volume Manager disk set is automatically registered with Sun Cluster software as an svm or sds device group, but replication information is not synchronized at that time. For newly created vxvm and rawdisk device-group types, you do not need to manually synchronize replication information for the disks. When you register a VxVM disk group or a raw-disk device group with Sun Cluster software, the software automatically discovers any replication information on the disks. To change the order-of-node preference list from false to true, you must specify in the nodelist all the nodes that currently exist in the device group. You must also set the preferenced suboption to true. If you do not specify the preferenced suboption with the change form of the command, the already established true or false setting is used. If a disk group should be accessed by only one node, it should be configured with the localonly property set to true. This property setting puts the disk group outside the control of Sun Cluster software. Only one node can be specified in the node list to create a localonly disk group. To change a local-only disk group to a regular VxVM disk group, set the localonly property to false. -r Remove the specified VxVM device group from the cluster. The -r (remove) option removes a VxVM device group from the Sun Cluster device-groups configuration. You can also use this form of command to remove the nodes from the VxVM device group configuration. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a VxVM device group, change the order of the potential primary nodes, change the preference and fail- back policy for the device group, change the desired number of secondaries, and remove the VxVM device group from the cluster configura- tion. host1# scconf -a -D type=vxvm,name=diskgrp1,nodelist=host1:host2:host3,preferenced=false,failback=enabled host1# scconf -c -D name=diskgrp1,nodelist=host2:host1:host3,preferenced=true,failback=disabled,numsecondaries=2 sync host1# scconf -r -D name=diskgrp1,nodelist=node1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 2 Aug 2006 scconf_dg_vxvm(1M)
All times are GMT -4. The time now is 02:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy