Running A Redundancy Check; Resetting A Controller; Enabling A Controller Data Transfer - IBM System Storage DS3000 Programming Manual

The script command set provides two commands to define media scan properties:
v set logicalDrive
v set storageSubsystem
The set logicalDrive command enables a media scan for the logical drive. The command takes this
form:
set (allLogicalDrives | logicalDrive [logicalDriveName] | logicalDrives
[logicalDriveName1 ... LogicalDriveNameN] | logicalDrive <wwID>)
mediaScanEnabled=(TRUE | FALSE)
The set storageSubsystem command defines how frequently a media scan is run on a storage subsystem.
The command takes this form:
set storageSubsystem mediaScanRate=(disabled | 1-30)
The mediaScanRate values define the number of days over which the media scan runs. Valid values are
disabled, which turns off the media scan; or 1 day to 30 days, where 1 day is the fastest scan rate, and 30
days is the slowest. A value other than what is shown will not allow the media scan to function.

Running a Redundancy Check

Redundancy checks are performed when media scans are run. (For a description about how to set up and
run media scans, see "Running a Media Scan" on page 11-1.) During a redundancy check, all of the data
blocks in a logical drive are scanned, and, depending on the RAID level, deteriorated data is corrected.
Correction is performed as follows:
v For RAID 3, RAID 5, or RAID 6 logical drives, redundancy is checked and repaired.
v For RAID 1 logical drives, the data is compared between the mirrored disk drives and data
inconsistencies are repaired.
v RAID 0 logical drives have no redundancy.
Before you can run a redundancy check, you must enable redundancy checking by using the set
logicalDrive command. The command takes this form:
set (allLogicalDrives | logicalDrive [logicalDriveName] | logicalDrives [logicalDriveName1 ...
logicalDriveNameN] | logicalDrive <wwID>) redundancyCheckEnabled=(TRUE | FALSE)

Resetting a Controller

Important: When you reset a controller, the controller is no longer available for I/O operations until the
reset is complete. If a host is using logical drives that are owned by the controller being reset, the I/O
that is directed to the controller is rejected. Before resetting the controller, either make sure that the
logical drives that are owned by the controller are not in use, or make sure that a multi-path driver is
installed on all of the hosts that are using these logical drives.
Resetting a controller is the same as rebooting the controller processors. To reset a controller, use this
command:
reset controller [(a | b)]

Enabling a Controller Data Transfer

At times, a controller might become quiescent while running diagnostics. If this condition occurs, the
controller might become unresponsive. To revive a controller that has become quiescent while running
diagnostics, use this command:
enable controller [(a | b)] dataTransfer
11-2
IBM System Storage DS3000, DS4000, and DS5000: Command Line Interface and Script Commands Programming Guide