Hardware Installation
PixelStor 5000 User Manual
Rev. 1, May 2013
4-60
Priority
Inspection Read may be run in the background at one of three different priority levels. This
determines how much time is allocated to Inspection Read by the system. Inspection Read will
automatically relinquish the CPU during heavy CPU activity.
Logging
The Inspection Read process reports errors only on the local controller where the process was
initiated. Errors and process output is recorded in /var/log/messages and KEM log files.
Inspection Read creates a log message after each device has been successfully inspected.
Devices to Read
Inspection Read will access all sectors within each healthy, non-building; non RAID-0 Disk
Group and spare disk drives.
Device Type
Action
RAID 0 Device
Do Not Read
Healthy RAID Device
(not RAID 0, Not during initial build)
Read
Healthy RAID Device
(not RAID 0, During initial build)
Do Not Read
Degraded RAID Device
(not rebuilding on spare disk)
Do Not Read
Degraded RAID Device
(During rebuild on spare disk)
Do Not Read
Unhealthy RAID Device
Do Not Read
Orphan disk
Do Not Read
Spare disk
Read
Table 4-2
Inspection Read Action Table
Inspection Read monitors the status of Disk Groups and will stop an inspection if the status of
the Disk Group changes to a “Do Not Read” state listed in the previous table.
Starting Inspection Read
Inspection Read may be started from the Storage Manger or from the CLI. This section
describes using Inspection Read through the Console Manager. To learn how to use Inspection
read from the command line interface, issue the command daisnpread
–h from the CLI console.