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

Verifying a vdisk, Tools > Expand Vdisk, Expand Vdisk, View > Overview, Start Verify Utility

Page 84 highlights

Before expanding a vdisk Back up the vdisk's data so that if you need to stop expansion and delete the vdisk, you can move the data into a new, larger vdisk. To expand a vdisk 1. In the Configuration View panel, right-click a vdisk and select Tools > Expand Vdisk. Information appears about the selected vdisk and all disks in the system. • In the Disk Selection Sets table, the number of white slots in the vdisk's Disks field shows how many disks you can add to the vdisk. • In the enclosure view or list, only suitable available disks are selectable. 2. Select disks to add. 3. Click Expand Vdisk. A confirmation dialog appears. 4. Click Yes to continue; otherwise, click No. If you clicked Yes, a processing dialog appears. 5. Click OK. The expansion's progress is shown in the View > Overview panel. Verifying a vdisk If you suspect that a redundant (mirror or parity) vdisk has a problem, you can run the Verify utility to check the vdisk's integrity. For example, if the storage system was operating outside the normal temperature range, you might want to verify its vdisks. The Verify utility checks whether the redundancy data in the vdisk is consistent with the user data in the vdisk. For RAID 3, 5, 6, and 50, the utility checks all parity blocks to find data-parity mismatches. For RAID 1 and 10, the utility compares the primary and secondary disks to find data inconsistencies. Verification can last over an hour, depending on the size of the vdisk, the utility priority, and the amount of I/O activity. When verification is complete, the number of inconsistencies found is reported with event code 21 in the event log. Such inconsistencies can indicate that a disk in the vdisk is going bad. For information about identifying a failing disk, use the SMART option (see Configuring SMART on page 47). You can use a vdisk while it is being verified. If too many utilities are running for verification to start, either wait until those utilities have completed and try again, or abort a utility to free system resources. If you abort verification, you cannot resume it; you must start it over. To verify a vdisk 1. In the Configuration View panel, right-click a redundant vdisk and select Tools > Verify Vdisk. 2. Click Start Verify Utility. A message confirms that verification has started. 3. Click OK. The panel shows the verification's progress. To abort vdisk verification 1. In the Configuration View panel, right-click a redundant vdisk and select Tools > Verify Vdisk. 2. Click Abort Verify Utility. A message confirms that verification has been aborted. 3. Click OK. Scrubbing a vdisk The system-level Vdisk Scrub option (see Configuring background scrub for vdisks on page 51) automatically checks all vdisks for disk defects. If this option is disabled, you can still perform a scrub on a selected vdisk. The scrub utility analyzes a vdisk to detect, report, and store information about disk defects. Vdisk-level errors reported include: hard errors, media errors, and bad block replacements (BBRs). Disk-level errors reported include: metadata read errors, SMART events during scrub, bad blocks during scrub, and new disk defects during scrub. For RAID 3, 5, 6, and 50, the utility checks all parity blocks to find data-parity mismatches. For RAID 1 and 10, the utility compares the primary and secondary disks to find data inconsistencies. For NRAID and RAID 0, the utility checks for media errors. This utility does not fix defects. 84 Using system tools

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

84
Using system tools
Before expanding a vdisk
Back up the vdisk’s data so that if you need to stop expansion and delete the vdisk, you can move the data
into a new, larger vdisk.
To expand a vdisk
1.
In the Configuration View panel, right-click a vdisk and select
Tools > Expand Vdisk
. Information
appears about the selected vdisk and all disks in the system.
In the Disk Selection Sets table, the number of white slots in the vdisk’s Disks field shows how many
disks you can add to the vdisk.
In the enclosure view or list, only suitable available disks are selectable.
2.
Select disks to add.
3.
Click
Expand Vdisk
. A confirmation dialog appears.
4.
Click
Yes
to continue; otherwise, click
No
. If you clicked Yes, a processing dialog appears.
5.
Click
OK
. The expansion’s progress is shown in the
View > Overview
panel.
Verifying a vdisk
If you suspect that a redundant (mirror or parity) vdisk has a problem, you can run the Verify utility to check
the vdisk’s integrity. For example, if the storage system was operating outside the normal temperature
range, you might want to verify its vdisks. The Verify utility checks whether the redundancy data in the
vdisk is consistent with the user data in the vdisk. For RAID 3, 5, 6, and 50, the utility checks all parity
blocks to find data-parity mismatches. For RAID 1 and 10, the utility compares the primary and secondary
disks to find data inconsistencies.
Verification can last over an hour, depending on the size of the vdisk, the utility priority, and the amount of
I/O activity. When verification is complete, the number of inconsistencies found is reported with event
code 21 in the event log. Such inconsistencies can indicate that a disk in the vdisk is going bad. For
information about identifying a failing disk, use the SMART option (see
Configuring SMART
on page 47).
You can use a vdisk while it is being verified.
If too many utilities are running for verification to start, either wait until those utilities have completed and
try again, or abort a utility to free system resources. If you abort verification, you cannot resume it; you
must start it over.
To verify a vdisk
1.
In the Configuration View panel, right-click a redundant vdisk and select
Tools > Verify Vdisk
.
2.
Click
Start Verify Utility
. A message confirms that verification has started.
3.
Click
OK
. The panel shows the verification’s progress.
To abort vdisk verification
1.
In the Configuration View panel, right-click a redundant vdisk and select
Tools > Verify Vdisk
.
2.
Click
Abort Verify Utility
. A message confirms that verification has been aborted.
3.
Click
OK
.
Scrubbing a vdisk
The system-level Vdisk Scrub option (see
Configuring background scrub for vdisks
on page 51)
automatically checks all vdisks for disk defects. If this option is disabled, you can still perform a scrub on a
selected vdisk.
The scrub utility analyzes a vdisk to detect, report, and store information about disk defects. Vdisk-level
errors reported include: hard errors, media errors, and bad block replacements (BBRs). Disk-level errors
reported include: metadata read errors, SMART events during scrub, bad blocks during scrub, and new
disk defects during scrub. For RAID 3, 5, 6, and 50, the utility checks all parity blocks to find data-parity
mismatches. For RAID 1 and 10, the utility compares the primary and secondary disks to find data
inconsistencies. For NRAID and RAID 0, the utility checks for media errors. This utility does not fix defects.