![3Ware 720-0192-00 Manual Download Page 81](http://html1.mh-extra.com/html/3ware/720-0192-00/720-0192-00_manual_3236248081.webp)
Chapter 2. CLI Syntax Reference
73
3ware SAS/SATA RAID Controller CLI Guide, Version 9.5.2
2 = faster I/O; slower verify
1 = fastest I/O; slowest verify
For 9550SX(U) and earlier controllers, and for SE/SA controllers running
firmware 9.5 and 9.5.0.1, disabling verify with this command turns off the
verify schedule. In this case, if a verify is manually started, it should begin
right away.
For 9650SE and 9690SA controllers running firmware 9.5.1 or later, enabling
verify with this command is equivalent to using the
/cx set verify=advanced
command, while disabling verify with this command is equivalent to using the
/cx set verify=basic
command without specifying a preferred start day and
time (the default of Friday at midnight is used.) For more information, see “/
cx set verify=advanced|basic|1..5” on page 73.
You can view the verify schedule to be enabled or disabled with the command
“/cx show verify” on page 55. You can add verify task slots to the schedule
using the command “/cx add verify=ddd:hh:duration” on page 67. You can
remove verify task slots from the schedule with the “/cx del verify=slot_id”
on page 69.
/c
x
set verify=advanced|basic|1..5
This command only applies to 9650SE and the 9690SA RAID controllers
running 9.5.1 or later.
This command is effectively the same as the
set verify
command. Setting
verify to
advanced
enables the advanced Verify Task Schedule, which can
include a series of up to 7 days and times. Setting verify to
basic
creates a
weekly schedule with one specific day and time, and disables the series of
scheduling slots associated with the advanced Verify Task Schedule. For more
about the basic schedule, see “/cx set verify=basic [pref=ddd:hh]”, below.
The priority of verify versus I/O operations is specified with
1..5,
where 5 is
more resources and 1 the least. Setting this value to 1 implies fastest I/O, and
5 implies fastest verify.
Note:
In previous versions of the CLI, 1 was incorrectly reported to be the fastest
verify rate, and 5 was incorrectly reported to be the slowest—the opposite of the
actual settings. In 9.5.2, the scale is reported correctly, as described above, with 5
the fastest verify rate.
Note:
If you want verifications to occur automatically, when enabling the verify
schedule you must also remember to enable the autoverify setting for the units to be
verified. For more information see “/cx/ux set autoverify=on|off” on page 92.
Summary of Contents for 720-0192-00
Page 3: ......