![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1614831.1 : Sun Storage 2500, 2500-M2, and 6000 Arrays: How Virtual Disk (VDisk) Defragmentation Works
Defragmentation on VDisk and the job it creates. Applies to:Sun Storage 2530 Array - Version Not Applicable and laterSun Storage 2540-M2 Array - Version Not Applicable and later Sun Storage 2530-M2 Array - Version Not Applicable and later Sun Storage 2510 Array - Version Not Applicable and later Sun Storage 6580 Array - Version All Versions and later Information in this document applies to any platform. PurposeThe intent of this document is to explain what occurs when defragmentation is running. Defragmentation is carried out from the Sun Storage Common Array Manager (CAM) browser user interface (BUI) or command line (CLI). For more detailed information about the effects of defragmentation and when to consider running defragmentation, refer to <Document 1007871.1> Cannot Use All of the Remaining Capacity on a Sun StorEdge 6000 or 2500 Arrays to Create a Volume.
DetailsWhen you initiate a defragmentation process, you indicate a virtual disk, or vdisk. You might therefore expect that a single job is created. In fact the operation affects all of the volumes within the virutal disk, and a separate job is created for each volume. When monitoring the progress of defragmentation, it is important to realize that multiple jobs may be involved. In some cases when the size of a volume is small, the job may not even be reported, as the time to defragment is too short to be registered and displayed. You can track the progress of defragmentation jobs by examining the majorEventLog file (MEL) that is captured as part of the supportData for the array. Please refer to <Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays. The MEL contains the internal event logs for the array. The MEL excerpt below shows the start and stop of the defragmentation for the volume vol-data1 in the virtual disk called VirtualDisk 3. The start of the defragmentation is reported as: Date/Time: Tue Jan 14 08:53:57 CET 2014
Sequence number: 17258 Event type: 500F Event category: Command Priority: Informational Description: Start virtual disk defragment Event specific codes: 0/0/0 Component type: VirtualDisk Component location: VirtualDisk 3 Logged by: Controller in slot A
Date/Time: Tue Jan 14 08:53:57 CET 2014
Sequence number: 17257 Event type: 2028 Event category: Notification Priority: Informational Description: Modification (reconfigure) started Event specific codes: 0/0/0 Component type: Volume Component location: vol-data1 Logged by: Controller in slot A .. .. .. .. Date/Time: Tue Jan 14 21:25:07 CET 2014 Sequence number: 17260 Event type: 2029 Event category: Notification Priority: Informational Description: Modification (reconfigure) completed Event specific codes: 0/0/0 Component type: Volume Component location: vol-data1 Logged by: Controller in slot A
sscs list -a <array name as seen in CAM> jobs
sscs list -a 6540-array jobs
Job ID: 2014.01.15.13.38.24.106 Status: Done Job ID: 2014.01.15.13.40.29.382 Status: Done Job ID: 2014.01.15.13.42.32.874 Status: In Progress
Where `sscs` is under:
Solaris: /opt/SUNWstkcam/bin/ Linux: /opt/sun/cam/bin/ Windows: C:\Program Files\Sun\Common Array Manager\bin sscs list -a <array name as seen in CAM> jobs <job ID to view>
Example: # ./sscs list -a 6540-array jobs 2014.01.15.13.38.24.106
# ./sscs list -a 6540-array jobs 2014.01.15.13.42.32.874
References<NOTE:1007871.1> - Cannot Use All of the Remaining Capacity on a Sun StorEdge 6000 or 2500 Arrays to Create a Volume.Attachments This solution has no attachment |
||||||||||||
|