Serial Split Brain detected in solaris10 Post: 302409913

Sponsored Content

Operating Systems Solaris Serial Split Brain detected in solaris10 Post 302409913 by reborg on Friday 2nd of April 2010 11:10:04 PM

04-03-2010

Administrator Emeritus

That's very good.

Now a couple of observations on your setup.

1. Mixing internal and external disks in a volume is a bad idea ( prefereably not in the same DG )

2. If you have to use the internal disks put the log plex on the external disks with one data disk and the spare on the internal disks.

The reason for both of the above is that if you get a failure it is more likely to be consistent. Even if the external disks all fail you should be able to pull the internal disks and reattach the external ones. You will be able to rebuild the one internal data disk from parity.

If you can avoid using the internal disk at all then do. A failure of the external disks is likely to be self consistent in such a scenario and is much easier to recover.

3. Get the SCSI csi controller checked and check for patches for bugs that cause controller failure-like sysmptoms it is likely the original cause of your problem was one or other.

---------- Post updated at 04:10 AM ---------- Previous update was at 04:06 AM ----------

Quote:

Originally Posted by upengan78

That worked fine as well. no errors at mount command. Also, I can create files/ directories/rmdir ..worked out fine.

Many thanks! Appreciate your help really!!...God bless you.

You're welcome. It's always rewarding to get to the bottom of a problem and all the more enjoyable if the person at the other end doesn't panic or get flustered.

reborg

View Public Profile for reborg

Find all posts by reborg

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Brain Bench Certification

Hi, Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros...

2. Programming

C Brain Teaser

Dear Gurus, I have encountered a C question, which I thought of sharing with you. This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this.. Write a C program to do a small task(lets say just simply printing a "Hello...

3. Programming

Brain Teaser Extended

Hi Gurus, To the Brain Teaser, if I add another condition, say the executable should not be altered, how the program should be altered? (no perl please, purely C). I forgot to mention this condition my staff had mentioned. ( forgot then and got now :D ) The program executed the first time...

4. Ubuntu

Ubuntu 9.04 Serial application to telnet to serial device

Hello! I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a...

5. What is on Your Mind?

The Human Brain project

A global group of scientists are spending the next ten years and a billion dollars to try and develop a computer simulation of the brain: https://www.humanbrainproject.eu/ I always found it fascinating that the brain can understand itself. This almost sounds like in a few years the computer...

LEARN ABOUT NETBSD

bioctl

BIOCTL(8)						    BSD System Manager's Manual 						 BIOCTL(8)

NAME

     bioctl -- RAID management interface

SYNOPSIS

     bioctl device command [arg [...]]

DESCRIPTION

     RAID device drivers which support management functionality can register their services with the bio(4) driver.  bioctl then can be used to
     manage the RAID controller's properties.

COMMANDS

     The following commands are supported:

     show [disks | volumes]
			 Without any argument by default bioctl will show information about all volumes and the logical disks used on them.  If
			 disks is specified, only information about physical disks will be shown.  If volumes is specified, only information about
			 the volumes will be shown.

     alarm [disable | enable | silence | test]
			 Control the RAID card's alarm functionality, if supported.  By default if no argument is specified, its current state
			 will be shown.  Optionally the disable, enable, silence, or test arguments may be specified to enable, disable, silence,
			 or test the RAID card's alarm.

     blink start channel:target.lun | stop channel:target.lun
			 Instruct the device at channel:target.lun to start or cease blinking, if there's ses(4) support in the enclosure.

     hotspare add channel:target.lun | remove channel:target.lun
			 Create or remove a hot-spare drive at location channel:target.lun.

     passthru add DISKID channel:target.lun | remove channel:target.lun
			 Create or remove a pass-through device.  The DISKID argument specifies the disk that will be used for the new device, and
			 it will be created at the location channel:target.lun.  NOTE: Removing a pass-through device that has a mounted filesys-
			 tem will lead to undefined behaviour.

     check start VOLID | stop VOLID
			 Start or stop consistency volume check in the volume with index VOLID.  NOTE: Not many RAID controllers support this fea-
			 ture.

     create volume VOLID DISKIDs [SIZE] STRIPE RAID_LEVEL channel:target.lun
			 Create a volume at index VOLID.  The DISKIDs argument will specify the first and last disk, i.e.: 0-3 will use the disks
			 0, 1, 2, and 3.  The SIZE argument is optional and may be specified if not all available disk space is wanted (also
			 dependent of the RAID_LEVEL).	The volume will have a stripe size defined in the STRIPE argument and it will be located
			 at channel:target.lun.

     remove volume VOLID channel:target.lun
			 Remove a volume at index VOLID and located at channel:target.lun.  NOTE: Removing a RAID volume that has a mounted
			 filesystem will lead to undefined behaviour.

EXAMPLES

     The following command, executed from the command line, shows the status of the volumes and its logical disks on the RAID controller:

     $ bioctl arcmsr0 show
     Volume Status	 Size	      Device/Label   RAID Level Stripe
     =================================================================
	  0 Building	 468G  sd0 ARC-1210-VOL#00	 RAID 6  128KB	0% done
	0:0 Online	 234G	      0:0.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
	0:1 Online	 234G	      0:1.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
	0:2 Online	 234G	      0:2.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
	0:3 Online	 234G	      0:3.0 noencl <WDC WD2500YS-01SHB1 20.06C06>

     To create a RAID 5 volume on the SCSI 0:15.0 location on the disks 0, 1, 2, and 3, with stripe size of 64Kb on the first volume ID, using all
     available free space on the disks:

	   $ bioctl arcmsr0 create volume 0 0-3 64 5 0:15.0

     To remove the volume 0 previously created at the SCSI 0:15.0 location:

	   $ bioctl arcmsr0 remove volume 0 0:15.0

SEE ALSO

     arcmsr(4), bio(4), cac(4), ciss(4), mfi(4)

HISTORY

     The bioctl command first appeared in OpenBSD 3.8, it was rewritten for NetBSD 5.0.

AUTHORS

     The bioctl interface was written by Marco Peereboom <marco@openbsd.org> and was rewritten with multiple features by
     Juan Romero Pardines <xtraeme@NetBSD.org>.

BSD
								  March 16, 2008							       BSD