Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: VCS triggerring panic on 1 node, root disk under SVM
Top Forums UNIX for Advanced & Expert Users VCS triggerring panic on 1 node, root disk under SVM Post 302811113 by amlanroy on Thursday 23rd of May 2013 04:29:13 AM
Old 05-23-2013
VCS triggerring panic on 1 node, root disk under SVM
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.

--------------------------------------------------------------------------------------------
From VCS engine log,

2013/04/20 02:34:18 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze ORACLE_PRASAPDB_Group from localhost
2013/04/21 10:38:14 VCS INFO V-16-1-10196 Cluster logger started
2013/04/21 10:38:14 VCS NOTICE V-16-1-11022 VCS engine (had) started


From OS messages,

Apr 21 04:00:26 prdagwn1 genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c1t0d0s1, offset 65536, content: kernel Apr 21 04:00:31 prdagwn1 scsi: [ID 365881 kern.info] /pci@400/pci@0/pci@8/scsi@0 (mpt0):
Apr 21 04:00:31 prdagwn1 Log info 31140000 received for target 1.
Apr 21 04:00:31 prdagwn1 scsi_status=0, ioc_status=8048, scsi_state=c
Apr 21 04:01:32 prdagwn1 md_stripe: [ID 641072 kern.warning] WARNING: md: d20: read error on /dev/dsk/c1t1d0s0 Apr 21 04:02:32 prdagwn1 last message repeated 1 time Apr 21 04:03:33 prdagwn1 md_stripe: [ID 641072 kern.warning] WARNING: md: d20: write error on /dev/dsk/c1t1d0s0 Apr 21 04:07:42 prdagwn1 genunix: [ID 409368 kern.notice] ^M100% done: 405019 pages dumped, compression ratio 3.71, Apr 21 04:07:42 prdagwn1 genunix: [ID 851671 kern.notice] dump succeeded

I can see the md has problem in write access on disk slice c1t1d0s0 which has /var included. If the directory /var is in question with access problem, VCS GAB would trigger system panic due to client process failure as VCS daemon 'had' can't access the /var directory.

Oracle suggested to replace disk1 after initial investigation. This is the same disk that failed 3 weeks back

Is there any setting we can do in VCS to accomodate delayed write in disk under SVM ? Or do we move from SVM to VxVM ?
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk replacement with svm

I dont even know what raid level this is, but its raid 5 mirrored from the looks of it. I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. Solaris

Why didn't she panic? (Sol 10 + SVM + HDS)

Hi folks, the following incident occured today: by mistake one of our renowned administrators deleted the complete zoning for a 25K domain running solaris 10. Thus the system lost all of it's external disks. We've got oracle datafiles and oracle software residing on those lost... (6 Replies)
Discussion started by: MikaBaghinen
6 Replies

3. Solaris

mirroring root disk using svm - but no free slices for metadb's

Hi all, we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this? In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies

4. Solaris

Root Disk mirroring in SVM

Dear All, Please help me to configure root mirroring using SVM in Solaris 9. Thanks and Regards, Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies

5. Solaris

SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node

Hi, Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies

6. Hardware

Cannot mount root - Panic

Hi Guys, I just tried to reboot my server, but it seems to be panicing and unable to mount the root disk. The filesystem is supposed to be ufs, so im not sure why its talking about vfs. At the moment it's just stuck in a loop of Reboot-panic-reboot. Any ideas? A. SunOS Release 5.10... (1 Reply)
Discussion started by: A-Train
1 Replies

7. Solaris

Root disk mirroring in SVM

I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies

8. Solaris

VCS - 3 node - IP change

Hey Admins, I need steps to do an IP changes on 3-node VCS cluster. All IP's (public, cluster IP's, backup IP, etc.)want to change. We have a downtime scheduled. Please let me know the steps to do so. Thanks in advance. (5 Replies)
Discussion started by: snchaudhari2
5 Replies

9. UNIX for Beginners Questions & Answers

SVM recover root

Hi,, i have a solaris 10 machine , that let the root password expire.. I am trying to recover from failsafe mode. In the old days it was rater simple , boot to cdrom , mount the root disk, /a cd /a and wipe out root pw string.. Now i have to try and do it remotely , from failsafe and this... (2 Replies)
Discussion started by: goya
2 Replies

10. AIX

Crash dump and Panic message : RSCT Dead Man Switch Timeout for HACMP; halting non-responsive node

Dear all i have two aix system -Model : P770 -OS version: AIX 6.1 -patch level : 6100-07-04-1216 -ha version : HACMP v 6.1.0.8 -host : A, B last Wednesday, my B system suddenly went down with crash dump. after 1 minute, A system went down with crash dump. I checked the dump of A-system... (6 Replies)
Discussion started by: tomato00
6 Replies

LEARN ABOUT HPUX

vxbrk_rootmir

vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME

       vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation

SYNOPSIS

       /etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b]     [-t tasktag] {daname|dmname}

DESCRIPTION

       The  vxbrk_rootmir  command  creates  a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the
       broken-off mirror into a completely separate root disk that is suitable for booting by itself.

       Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks.  A  valid	root  mirror  disk
       should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained.

       The  given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror.  If so,
       the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk.	If the specified  disk	is  not  a
       valid  root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur-
       rent VxVM root disk.  After the mirroring operation is complete, the mirror is then broken off, and regenerated into  a	unique	VxVM  root
       disk.

OPTIONS

       -b   Uses  the  setboot	command  to set the alternate boot disk to the specified disk.	If the -v option is also specified, information is
	    displayed about the current setboot settings.

       -g diskgroup
	    Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created	if  it	does  not  already
	    exist.   If  the  disk group already exists, the broken-off mirror is added to it.	If this option is not specified, the disk group of
	    the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk
	    group to prevent the mirror from being automatically imported.

       -t tasktag
	    Marks  any tasks that are registered to track the progress of an  operation with the specified tag, tasktag.  This option is passed to
	    vxrootmir if it is necessary first to mirror the specified disk that is to be broken off.

       -v   Displays verbose output, including timestamps for operations that are in progress.	This option is passed to vxrootmir if it is neces-
	    sary first to mirror the specified disk that is to be broken off.

ARGUMENTS

       daname	 Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0).

       dmname	 Specifies the disk to be used as the broken off  mirror by its disk media name (such as rootdisk03).

EXAMPLES

       This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror:

       /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0
       VxVM vxbrk_rootmir INFO V-5-2-4023 17:47:
	 Checking specified disk(s) for presence and type
       VxVM vxbrk_rootmir INFO V-5-2-4025 17:47:
	 DA c4t15d0s2, DM rootdisk06 is a valid root mirror
       VxVM vxbrk_rootmir INFO V-5-2-4052 17:47:
	 Saving configuration data for later restoration
       VxVM vxbrk_rootmir INFO V-5-2-4022 17:47:
	 Breaking off root mirror on DA c4t15d0s2
       VxVM vxbrk_rootmir INFO V-5-2-4054 17:47:
	 Setting broken off mirror on c4t15d0s2 as unique root disk
       VxVM vxbrk_rootmir INFO V-5-2-2566 17:47:
	 Preparing disk c4t15d0s2 as a VxVM root disk
       VxVM vxbrk_rootmir INFO V-5-2-4046 17:47:
	 Patching devnodes, fstab and volboot file in new Root FS
       VxVM vxbrk_rootmir INFO V-5-2-4045 17:47:
	 Patching /stand/bootconf file to contain new root disk
       VxVM vxbrk_rootmir INFO V-5-2-2462 17:48:
	 Current setboot values:
       VxVM vxbrk_rootmir INFO V-5-2-4048 17:48:
	 Primary:   0/0/2/0.2.0
       VxVM vxbrk_rootmir INFO V-5-2-4010 17:48:
	 Alternate: 0/2/1/0.8.0.255.2.5.0
       VxVM vxbrk_rootmir INFO V-5-2-4042 17:48:
	 Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk
       VxVM vxbrk_rootmir INFO V-5-2-4028 17:48:
	 Disk c4t15d0s2 is now a broken off root disk

       The  next  example  shows  the  command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be
       called to mirror the root disk first:

	      /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0
	      VxVM vxbrk_rootmir INFO V-5-2-4023 16:25:
		Checking specified disk(s) for presence and type
	      VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk
	      VxVM vxrootmir INFO V-5-2-2501 16:25:
		Gathering information on the current VxVM root configuration
	      VxVM vxrootmir INFO V-5-2-2441 16:25:
		Checking specified disk(s) for usability
	      VxVM vxrootmir INFO V-5-2-2566 16:25:
		Preparing disk c5t5d0 as a VxVM root disk
	      VxVM vxrootmir INFO V-5-2-3766 16:25:
		Disk c5t5d0 is now EFI partitioned disk c5t5d0s2
	      VxVM vxrootmir INFO V-5-2-2410 16:25:
		Adding disk c5t5d0s2 to brkdg as DM rootdisk03
	      VxVM vxrootmir INFO V-5-2-1646 16:25:
		Mirroring all volumes on root disk
	      VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol
	      VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol
	      VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol
	      VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol
	      VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol
	      VxVM vxrootmir INFO V-5-2-1616 16:40:
		Disk c5t5d0s2 is now a mirrored root disk
	      VxVM vxbrk_rootmir INFO V-5-2-4052 16:40:
		Saving configuration data for later restoration
	      VxVM vxbrk_rootmir INFO V-5-2-4022 16:40:
		Breaking off root mirror on DA c5t5d0s2
	      VxVM vxbrk_rootmir INFO V-5-2-4054 16:40:
		Setting broken off mirror on c5t5d0s2 as unique root disk
	      VxVM vxbrk_rootmir INFO V-5-2-2566 16:40:
		Preparing disk c5t5d0s2 as a VxVM root disk
	      VxVM vxbrk_rootmir INFO V-5-2-4046 16:41:
		Patching devnodes, fstab and volboot file in new Root FS
	      VxVM vxbrk_rootmir INFO V-5-2-4045 16:41:
		Patching /stand/bootconf file to contain new root disk
	      VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values:
	      VxVM vxbrk_rootmir INFO V-5-2-4048 16:41:
		Primary:   0/0/2/0.2.0
	      VxVM vxbrk_rootmir INFO V-5-2-4010 16:41:
		Alternate: 0/2/1/0.8.0.255.2.0.0
	      VxVM vxbrk_rootmir INFO V-5-2-4042 16:41:
		Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk
	      VxVM vxbrk_rootmir INFO V-5-2-4028 16:41:
		Disk c5t5d0s2 is now a broken off root disk

SEE ALSO

       vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M)

VxVM 5.0.31.1							    24 Mar 2008 						 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 01:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy