Справочник Пользователя для AMCC 9500S
Chapter 2. CLI Syntax Reference
48
3ware Serial ATA RAID Controller CLI Guide
--------------------------------------------------------------------------
u0 RAID-5 INITIALIZING 0 - 64K 521.466 ON OFF
Port Status Unit Size Blocks Serial
---------------------------------------------------------------
p0 NOT-PRESENT - - - -
p1 OK u0 76.33 GB 160086528 Y2NXL7FE
p2 NOT-PRESENT - - - -
p3 OK u0 76.33 GB 160086528 Y2NXLB9E
p4 NOT-PRESENT - - - -
p5 OK u0 76.33 GB 160086528 Y2NXQPZE
p6 NOT-PRESENT - - - -
p7 OK u0 76.33 GB 160086528 Y2NXM4VE
p8 OK u0 74.53 GB 156301488 3JV3WTSE
p9 OK u0 74.53 GB 156301488 3JV3WRHC
p10 OK u0 74.53 GB 156301488 3JV3WQLQ
p11 OK u0 74.53 GB 156301488 3JV3WQLZ
Name OnlineState BBUReady Status Volt Temp Hours LastCapTest
---------------------------------------------------------------------------
bbu On Yes OK OK OK 0 xx-xxx-xxxx
/c
x
show verify
9000 series controllers support background tasks and allow you to schedule a
regular time when they occur.
regular time when they occur.
Verify is one of the supported background tasks. Rebuild and selftest are other
background tasks for which there are separate schedules. Migrate and
initialize are additional background tasks that follow the same schedule as
rebuild. For each background task, up to 7 time periods can be registered,
known as slots 1 through 7. Each task schedule can be managed by a set of
commands including add, del, show and set a task. Background task
schedules have a slot id, start-day-time, duration, and status attributes.
background tasks for which there are separate schedules. Migrate and
initialize are additional background tasks that follow the same schedule as
rebuild. For each background task, up to 7 time periods can be registered,
known as slots 1 through 7. Each task schedule can be managed by a set of
commands including add, del, show and set a task. Background task
schedules have a slot id, start-day-time, duration, and status attributes.
For details about setting up a schedule for background verify tasks, see
“Setting Up a Verify Schedule” on page 51.
“Setting Up a Verify Schedule” on page 51.
Verify activity verifies all units based on their unit type. Verifying RAID 1
involves checking that both drives contain the exact data. On RAID 5 and
RAID 6, the parity information is used to verify data integrity. RAID 10 and
50 are composite types and follow their respective array types. On 9000
series, non-redundant units such as RAID 0, JBOD, single, and spare, are also
verified (by reading and reporting un-readable sectors). If any parity
mismatches are found, the array will be automatically background initialized.
(For information about the initialization process, see the user guide that came
with your 3ware RAID controller.)
involves checking that both drives contain the exact data. On RAID 5 and
RAID 6, the parity information is used to verify data integrity. RAID 10 and
50 are composite types and follow their respective array types. On 9000
series, non-redundant units such as RAID 0, JBOD, single, and spare, are also
verified (by reading and reporting un-readable sectors). If any parity
mismatches are found, the array will be automatically background initialized.
(For information about the initialization process, see the user guide that came
with your 3ware RAID controller.)
The show verify command displays the current verify background task
schedule as illustrated below.
schedule as illustrated below.