Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1586828.1
Update Date:2017-05-12
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1586828.1 :   Sun Storage 3000 Arrays: What is the Meaning of Disk Status FORCLONE  


Related Items
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
  •  




Applies to:

Sun Storage 3310 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 3320 SCSI Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 3510 FC Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 3511 SATA Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Purpose

The command sccli> show disks may report a disk drive with a FORCLONE status.  You will see this condition when a clone operation has taken place. In the following example, we can see the sccli> show disks output before and after a clone. This document describes how the status got there and how to administer such conditions.

Before a clone has occurred:


sccli> show disks
Ch     Id      Size   Speed  LD     Status     IDs                      Rev
----------------------------------------------------------------------------
 2(3)   3  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0207
                                                   S/N 3HY0DYZT00007327
                                                  WWNN 20000004CFD8DF4A
 2(3)   4  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0307
                                                   S/N 3HY0DYNF00007327
                                                  WWNN 20000004CFD8DF88
 2(3)   5  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0307
                                                   S/N 3HY0DX3N00007328
                                                  WWNN 20000004CFD8E010
 2(3)   7  136.73GB   200MB  ld0    STAND-BY   SEAGATE ST314680FSUN146G 0207
                                                   S/N 3HY0D7Z200007327
                                                  WWNN 20000004CFD8DE74

After the clone has occurred:


sccli> show disks
Ch     Id      Size   Speed  LD     Status     IDs                      Rev
----------------------------------------------------------------------------
 2(3)   3  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0207
                                                   S/N 3HY0DYZT00007327
                                                  WWNN 20000004CFD8DF4A
 2(3)   4  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0307
                                                   S/N 3HY0DYNF00007327
                                                  WWNN 20000004CFD8DF88
 2(3)   5  136.73GB   200MB  ld0    ONLINE     SEAGATE ST314680FSUN146G 0307
                                                   S/N 3HY0DX3N00007328
                                                  WWNN 20000004CFD8E010
 2(3)   7  136.73GB   200MB  ld0    FORCLONE   SEAGATE ST314680FSUN146G 0207
                                                   S/N 3HY0D7Z200007327



The event log also records some information about the clone:

sccli> show events

Fri Oct 18 10:48:28 2013
[Primary]       Notification
LG:0 Logical Drive NOTICE:CHL:2 ID:5 Starting Clone


Fri Oct 18 10:50:29 2013
[Primary]       Notification
LG:0 Logical Drive NOTICE:CHL:2 ID:5 Clone Completed

Details

With the help of Self-Monitoring Analysis and Reporting Technology (SMART), disk drive failures can sometimes be predicted before they happen. For such drive showing symptoms of impending failure, system administrators can decide when to substitute a functional drive, either manually or automatically. This substitute process is called cloning.

  • Manual Cloning: System administrator can manually clone the failing drive, choosing a convenient time when system performance will not be adversely affected.
  • Automatic Cloning: The controller clones the failing drive automatically to a standby spare drive. This can be achieved by setting SMART drive parameters.

Whether it is Manual Cloning or Automatic Cloning, there are two options while cloning a failing drive:

  1. Replace after Clone:
    • Data on the source drive (the drive with the predicted error or any selected member drive) is cloned to a standby spare.
    • The spare drive then becomes the new source drive.
    • The status of the original source drive is redefined as a USED drive.
      
    DriveDrive Status while CloningDrive Status after completion of Cloning
    Source Drive Member Drive of a Logical Drive USED
    Destination Drive CLONING (in RAID Firmware Application display)
    IN-CLONE (under "sccli> show disks" output)
    Member Drive of the Logical Drive

     

  2. Perpetual Clone:
    • Data on the source drive (the drive with a predicted error or any selected member drive) is cloned to a standby spare.
    • The spare does not become the new source drive, the spare drive stays mirrored to the source drive until the source drive fails, or the perpetual clone is manually terminated.
    • The source drive remains a member of the logical drive.
    • Manual initialization of Perpetual Clone or Termination can only be performed by RAID firmware application menu.
      
    DriveDrive Status while CloningDrive Status after completion of Cloning
    Source Drive Member Drive of a Logical Drive Member Drive of the Logical Drive
    Destination Drive CLONING (in RAID Firmware Application display)
    IN-CLONE (under "sccli> show disks" output
    CLONE (in RAID Firmware Application display)
    FORCLONE (under "sccli> show disks" output)

     

    While the spare drive is mirroring the source drive and no other spare drive is available, any drive failure in the same logical drive forces the CLONE drive to give up the mirrored data and resume its original role. It becomes a spare drive again and rebuilds the failed drive.

     


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback