metadevices: how to test metadb (how to corrupt replicas/understanding replicas) Post: 302440992

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SDS and replicas

Hello, We are using Solstice Disk Suite on Solaris 2.7. We want to add two striped volume with six disks. On each disk, we take a slice and we create the stripe. That I want to know : Is it necessary to add two replicas on the same slice on the new disks, as made before on the others...

2. Solaris

insufficient metadevice database replicas ERROR

First I would like to thank this forum for assisting me in setting up my 1st sunbox. Could not have done it if it had not been for you guys and google :D I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully. I am now looking at configuring...

3. Solaris

Problem with DiskSuite replicas

Good morning, I have Solstice disk suite installed on my server. One disk broke so I sostitute it. A replica was present on this disk. I had delete and then recreate it with commands metadb -d and metadb -a. Now when I inquire for the status of replicas I see this: stp11# metadb -i ...

4. Solaris

Metadevices in mirroring ?

Hi Guys. I have the follow disk mappig.... My doubt is that the filesystem root is in mirroring. I can see this in the configuration but , I dont know exactly if this in mirroring mean disk in RAID. In short: Watching the configuration...Can I said if the filesystem / is in Raid? ...

5. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the...

6. Solaris

Solaris Volume Manger - Database Replicas Question - Benefits of Increasing Default Size?

Hey all! I was hoping someone knew anything about this one... I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately) Now I know you can increase this amount but is there any point? The reason I am asking this is that I've setup mirroring on...

7. Solaris

Metadevices deleted

Hi Guys, We have an issue, all metadb's on system was deleted and the system was rebooted. the system is currented mounted in single-user mode . its a x86 server. the volumes under SVM is as follows. / /var and /usr please suggest Please use code tags <- click the...

8. Solaris

SVM - Metadevices are offline after changing hostname solaris x86

Hi , We are facing an issue on one of our solaris x86 server, After changing the hostname and a orderly reboot , all metadevices shows offline. please let us know the steps to restore back all metadevices to working state with this new hostname

9. Solaris

zfs raidz2 - insufficient replicas

I lost my system volume in a power outage, but fortunately I had a dual boot and I could boot into an older opensolaris version and my raidz2 7 drive pool was still fine. I even scrubbed it, no errors. However, the older os has some smb problems so I wanted to upgrade to opensolaris11. I...

10. Solaris

Creating metadevices

Hi I am new to SVM, but I would like to configure it in one of my servers. The setup is as follows: I have one server running solaris 10 , and is connected to a NetApp via iSCSI protocol. This is how I intend to do it: Ask the NetApp admin, to provide me with 3 LUNs of 100G each, them use the...

LEARN ABOUT LINUX

mdmonitord

mdmonitord(1M)						  System Administration Commands					    mdmonitord(1M)

NAME

       mdmonitord - daemon to monitor metadevices

SYNOPSIS

       /usr/sbin/mdmonitord [-t time_interval]

DESCRIPTION

       The mdmonitord utility is part of Solaris Volume Manager. It monitors and checks RAID1 (mirrors), RAID5 and hot spares.

       There are two methods for checking:

	 o  At fixed time intervals.

	 o  When a RAID-1 (mirror), RAID-5, or hot spare fails. A failure generates  an error event which triggers a check of these metadevices.

OPTIONS

       The following options are supported:

       -t	       Time  interval  in  seconds.   The  default value is 0, which causes probes to occur only upon an error. If you want to run
		       mdmonitord at a regular interval, a value of 1800 (seconds, every half hour) is recommended as a starting point.

EXIT STATUS

       The following exit values are returned:

       0	Successful completion.

       >0	An error occurred.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWmdu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       svcs(1), metaclear(1M), metadb(1M), metadetach(1M),  metahs(1M),  metainit(1M),	metaoffline(1M),  metaonline(1M),  metaparam(1M),  metare-
       cover(1M),   metarename(1M),   metareplace(1M),	 metaroot(1M),	metaset(1M),  metassist(1M),  metastat(1M),  metasync(1M),  metattach(1M),
       svcadm(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), smf(5), md(7D)

       Solaris Volume Manager Administration Guide

NOTES

       Since frequent probes can affect performance, it is recommended that the intervals between probes be limited.

       The mdmonitord service is managed by the service management facility, smf(5), under the service identifier:

       svc:/system/mdmonitor

       Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed  using  svcadm(1M).  The  ser-
       vice's status can be queried using the svcs(1) command.

SunOS 5.10							    25 Jul 2004 						    mdmonitord(1M)