HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 85

You can use a vdisk while it is being scrubbed. A scrub can last over an hour, depending on the size of the vdisk, the utility priority, and the amount of I/O activity. However, a "foreground" scrub performed by Media Scrub Vdisk is typically faster than a background scrub performed by Vdisk Scrub. When a scrub is complete, an event with code 207 is logged that specifies whether errors were found. For details, see the Event Descriptions Reference Guide. To scrub a vdisk 1. In the Configuration View panel, right-click a vdisk and select Tools > Media Scrub Vdisk. 2. Click Start Media Scrub Utility. A message confirms that the scrub has started. 3. Click OK. The panel shows the scrub's progress. To abort a vdisk scrub 1. In the Configuration View panel, right-click a vdisk and select Tools > Media Scrub Vdisk. NOTE: If the vdisk is being scrubbed but the Abort Media Scrub Utility button is grayed out, a background scrub is in progress. To stop the background scrub, disable the Vdisk Scrub option as described in Configuring background scrub for vdisks on page 51. 2. Click Abort Media Scrub Utility. A message confirms that the scrub has been aborted. 3. Click OK. Removing a vdisk from quarantine A vdisk having a fault-tolerant RAID level becomes quarantined if at least one of its disks is detected as missing after the storage system is powered up or while it is operating. Quarantine does not occur for NRAID or RAID-0 vdisks; if known-failed disks are missing; or if disks are missing after failover or recovery. Quarantine isolates the vdisk from host access, and prevents the system from changing the vdisk status to OFFL (offline). The number of missing disks determines the quarantine status; from least to most severe: • QTDN: Quarantined with down disks. At least one disk is missing; however, the vdisk could be accessed and would be fault tolerant. For instance, one disk is missing from a RAID-6. • QTCR: Quarantined critical. At least one disk is missing; however, the vdisk could be accessed. For instance, one disk is missing from a mirror or RAID-5. • QTOF: Quarantined offline. Multiple disks are missing and user data is incomplete. When a vdisk is quarantined, its disks are write-locked, its volumes become inaccessible, and it is not available to hosts until it is dequarantined. If there are interdependencies between the quarantined vdisk's volumes and volumes in other vdisks, quarantine may temporarily impact operation of those other volumes. For example, if the quarantined vdisk contains the snap pool used for snapshot, volume-copy, or replication operations, quarantine may temporarily cause the associated master volume to go offline; a volume-copy or replication operation can also be disrupted if an associated volume (snap pool, source volume, or destination volume) goes offline. Depending on the operation, the length of the outage, and the settings associated with the operation, the operation may resume automatically resume when the vdisk is dequarantined or may require manual intervention. A vdisk can remain quarantined indefinitely without risk of data loss. Examples of when quarantine might occur are: • At system power-up, a vdisk has fewer disks online than at the previous power-up. This may happen because a disk is slow to spin up, or because a drive enclosure is not powered up. The vdisk will be automatically dequarantined if the missing disks come online and the vdisk status becomes FTOL (fault tolerant and online), or if after 60 seconds the vdisk status is QTCR or QTDN. • A vdisk that is not running I/O loses redundancy plus one more disk. The vdisk will be automatically dequarantined if the missing disks come online and the vdisk status becomes FTOL, or if after 60 seconds the vdisk status is QTCR or QTDN. • A vdisk running I/O loses redundancy plus one more disk. The vdisk will be automatically dequarantined if the vdisk's status is QTCR or QTDN. HP P2000 G3 MSA System SMU Reference Guide 85