Sponsored Content
Full Discussion: Prediction of failures
Operating Systems Solaris Prediction of failures Post 302342086 by jlliagre on Friday 7th of August 2009 10:59:52 AM
Old 08-07-2009
You are still missing mine. Unless you expect a crystal ball to predict what will happen in the future with currently healthy components, the only reasonable way to prevent their future faults is by monitoring events coming from them. This is what SMF is designed to do.

Alternatively, if your goal is really to react to something that hasn't happened yet, you can pro-actively replace each disk after a period of use significantly smaller than its MTBF.

If you just care about your data, use something like RAIDZ2 with hot spares. Your system will happily survive two disks crashing at the same time and will automatically replace them by the spares.
 

4 More Discussions You Might Find Interesting

1. HP-UX

Communication Failures

HI ALL, I have been trying to install a particular software using remote linux server. some thing like this: rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>. The problem is whenever I try to install the product through a shell script the installation... (1 Reply)
Discussion started by: barun agarwal
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Event Prediction - New Sports Events

Hi, Some sports predictions suggestions. Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat. (9 Replies)
Discussion started by: ni2
9 Replies

3. Post Here to Contact Site Administrators and Moderators

Event Prediction - Euro 2012

Please add this new "event". (10 Replies)
Discussion started by: ni2
10 Replies

4. Solaris

11.0 to 11.2 update failures

Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support. FMRI = pkg://solaris/entire@0.5.11,5.11-0.175.1.15.0.4.0:20131230T203500Z When we run pkg update --accept the server contacts oracle, checks packages, finds about 700... (4 Replies)
Discussion started by: CptCarrot
4 Replies
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)
All times are GMT -4. The time now is 09:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy