Cx show verify – Avago Technologies 3ware SAS 9750-16i4e User Manual
Page 58
Chapter 2. CLI Syntax Reference
50
3ware SATA+SAS RAID Controller Card CLI Guide, Version 10.2
The show selftest command shows the current selftest background task
schedule as illustrated below. Selftests do not have a time duration since they
are completed momentarily.
//localhost> /c1 show selftest
Selftest Schedule for Controller /c1
========================================================
Slot Day Hour SMART
--------------------------------------------------------
1 Sun 12:00am enabled
2 Mon 12:00am enabled
3 Tue 12:00am enabled
4 Wed 12:00am enabled
5 Thu 12:00am enabled
6 Fri 12:00am enabled
7 Sat 12:00am enabled
/cx show verify
3ware controllers support background tasks and allow you to schedule a
regular time when they occur. Verify is one of the supported background
tasks, and the /cx show verify command shows you the current verify
schedule.
The Verify Task Schedule can be either basic or advanced. (For details about
the associated commands, see “/cx set verify=advanced|basic|1..5” on
page 66).
The basic Verify Task Schedule sets a single, weekly day and time for
verification to occur, and is designed for use with the autoverification of units.
The advanced Verify Task Schedule provides more control, with settings for a
maximum of seven time periods or slots known as 1 through 7.
For the advanced Verify Task Schedule, up to seven time periods can be
registered, known as slots 1 through 7. You can manage this task schedule
with a set of commands including add, del, show, and set a task. When you
add a schedule you can set start day, start hour, and duration attributes.
Rebuilds, migrations, and initializations follow similar schedule formats.
For details about setting up a schedule for verify tasks, see “Setting Up a
Verify Schedule” on page 60.
For details about setting a basic verify schedule, see “/cx set verify=basic
[pref=ddd:hh]” on page 66.
Verify activity verifies all units based on their unit type. Verifying RAID 1
involves checking that both drives contain the same data. On RAID 5 and
RAID 6, the parity information is used to verify data integrity. If any parity
mismatches are found, the array is automatically background initialized.
RAID 10 and 50 are composite types and follow their respective array types.
Nonredundant units such as RAID 0 and single are also verified verified by