10-15-2007
Sorry for the long winded details, but I'd imagine the more details the better!
Below is a section of the output from metastat -t
What basically seems to have happened is that the mirror has got itself confused as it needs repairing. looking at the iostat -En command, the hard disk do not show any errors. I haven't got any spare slices to move the damaged slice to as suggested with the metareplace command provided in the metastat output so I need to break the mirror, remove the mirror, then recreate it again so it starts to sync.
I have done this in the past but only via a gui screen and not through the text commands although I know it is possible.
Any help / guidance would be appreciated.
d27: Mirror
Submirror 0: d28
State: Needs maintenance Mon Sep 24 10:38:00 2007
Submirror 1: d29
State: Okay Mon Oct 28 16:36:45 2002
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 12581595 blocks (6.0 GB)
d28: Submirror of d27
State: Needs maintenance Mon Sep 24 10:38:00 2007
Invoke: metareplace d27 c1t8d0s4 <new device>
Size: 12581595 blocks (6.0 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Dbase State Reloc Hot Spare Time
c1t1d0s4 0 No Okay Yes Mon Oct 28 15:47:00 2002
c1t2d0s4 0 No Okay Yes Mon Oct 28 15:47:00 2002
c1t8d0s4 0 No Maintenance Yes Mon Sep 24 10:38:00 2007
d29: Submirror of d27
State: Okay Mon Oct 28 16:36:45 2002
Size: 12581595 blocks (6.0 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Dbase State Reloc Hot Spare Time
c1t4d0s4 0 No Okay Yes Mon Oct 28 15:47:37 2002
c1t5d0s4 0 No Okay Yes Mon Oct 28 15:47:37 2002
c1t11d0s4 0 No Okay Yes Mon Oct 28 15:47:37 2002
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is this correct if I have to create 2 partions of 100 Gigs each? (spread accross (6) 36 Gig drives)
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@0,0
1. c0t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
... (10 Replies)
Discussion started by: finster
10 Replies
2. Solaris
Has anybody every used Solstice DiskSuite? I am having trouble setting it up. I installed it without a problem, but do I really have to blow away the drives on the D1000 just to create a metastate database? (8 Replies)
Discussion started by: hshapiro
8 Replies
3. Solaris
According to the metadb man page:
Now based on italicized part, if a mirror only has a single replica and never crashes, it should still function.
Same with booting. I thought three replicas were necessary for the system to be able to come up but the comment about crashing tells me that... (2 Replies)
Discussion started by: BOFH
2 Replies
4. UNIX for Dummies Questions & Answers
I have a live Sunfire v440 server with 4 drives and I want to mirror drive 0 & 1 to 2 & 3. The on-board raid controller only allows for 1 live mirror. I was thinking of disksuite, but unfortunately the second disk is just one large partition with no free slices.
I was thinking of using... (0 Replies)
Discussion started by: csgonan
0 Replies
5. Solaris
Hi,
I am running Solaris 8 on Sun server with 2 hard drives. I have configured mirroring on the system using DiskSuite tool in order to have the same data on both disks. Now I want to perform some software upgrade and I would like to use the second disk as a backup disk. This means taking this... (3 Replies)
Discussion started by: carlossg
3 Replies
6. Solaris
Hello,
We have this system a SunFire 280R running Solaris 8 Generic_117350-46. It has 2 36GB disks in it. They are mirrored with DiskSuite 4.2.1.
When we execute a metastat all the devices report an Okay status, but when we go into metatool everything is in the Critical (maintenance)... (4 Replies)
Discussion started by: mgb
4 Replies
7. Solaris
hi all,
i want to mirror two disks with disksuite under solaris 9 , doses smeone can explain me Briefly the essential steps to do that plz ? (3 Replies)
Discussion started by: lid-j-one
3 Replies
8. Solaris
Hi all,
Do you know where I can download Soltice Disksuite 4.2 for Solaris 2.6 ?
I haven't the CD labeled “Solaris Server Intranet Extensions 1.0” .
Thanks in advance for your precious help.
Bests Regards
Hosni (2 Replies)
Discussion started by: hosni
2 Replies
9. Solaris
I have a SOlaris 10 v240 server. I'm installing disksuite to mirror the root drive D0 to D2. I also have one partition on disk 1 that I want to mirror to D3. I am not using ZFS right now.
Can I add that to my initial mirroring configuration or can I only mirror 1 drive to 1 drive?
Can I... (2 Replies)
Discussion started by: csross
2 Replies
10. Solaris
Hello all,
I have a Solaris Disksuite question :-
I will be adding 4 new drives to an E250 server and need will be configuring 2 striped volumes each consisting 2 new disks with SVM. In the end i will have 2 volumes each of 72gb. So in effect i will have 1 volume called D7 and another volume... (6 Replies)
Discussion started by: commandline
6 Replies
LEARN ABOUT LINUX
metareplace
metareplace(1M) System Administration Commands metareplace(1M)
NAME
metareplace - enable or replace components of submirrors or RAID5 metadevices
SYNOPSIS
/usr/sbin/metareplace -h
/usr/sbin/metareplace [-s setname] -e mirror component
/usr/sbin/metareplace [-s setname] mirror component-old component-new
/usr/sbin/metareplace [-s setname] -e RAID component
/usr/sbin/metareplace [-s setname] [-f] RAID component-old component-new
DESCRIPTION
The metareplace command is used to enable or replace components (slices) within a submirror or a RAID5 metadevice.
When you replace a component, the metareplace command automatically starts resyncing the new component with the rest of the metadevice.
When the resync completes, the replaced component becomes readable and writable. If the failed component has been hot spare replaced, the
hot spare is placed in the available state and made available for other hot spare replacements.
Note that the new component must be large enough to replace the old component.
A component may be in one of several states. The Last Erred and the Maintenance states require action. Always replace components in the
Maintenance state first, followed by a resync and validation of data. After components requiring maintenance are fixed, validated, and
resynced, components in the Last Erred state should be replaced. To avoid data loss, it is always best to back up all data before replacing
Last Erred devices.
OPTIONS
Root privileges are required for all of the following options except -h.
-e Transitions the state of component to the available state and resyncs the failed component. If the failed component has
been hot spare replaced, the hot spare is placed in the available state and made available for other hot spare replace-
ments. This command is useful when a component fails due to human error (for example, accidentally turning off a disk), or
because the component was physically replaced. In this case, the replacement component must be partitioned to match the
disk being replaced before running the metareplace command.
-f Forces the replacement of an errored component of a metadevice in which multiple components are in error. The component
determined by the metastat display to be in the ``Maintenance'' state must be replaced first. This option may cause data to
be fabricated since multiple components are in error.
-h Display help message.
-s setname Specifies the name of the diskset on which metareplace will work. Using the -s option will cause the command to perform its
administrative function within the specified diskset. Without this option, the command will perform its function on local
metadevices.
mirror The metadevice name of the mirror.
component The logical name for the physical slice (partition) on a disk drive, such as /dev/dsk/c0t0d0s2.
component-old The physical slice that is being replaced.
component-new The physical slice that is replacing component-old.
RAID The metadevice name of the RAID5 device.
EXAMPLES
Example 1: Recovering from Error Condition in RAID5 Metadevice
This example shows how to recover when a single component in a RAID5 metadevice is errored.
# metareplace d10 c3t0d0s2 c5t0d0s2
In this example, a RAID5 metadevice d10 has an errored component, c3t0d0s2, replaced by a new component, c5t0d0s2.
Example 2: Use of -e After Physical Disk Replacement
This example shows the use of the -e option after a physical disk in a submirror (a submirror of mirror d11, in this case) has been
replaced.
# metareplace -e d11 c1t4d0s2
Note: The replacement disk must be partitioned to match the disk it is replacing before running the metareplace command.
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
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4),
mddb.cf(4), md.tab(4), attributes(5), md(7D)
Solaris Volume Manager Administration Guide
SunOS 5.10 8 Aug 2003 metareplace(1M)