
|
| Monitoring Disk Resources | |
|
| Creating Disk Monitoring Requests | |
Table | Example for Interpreting the pv_summary for Mirrored Disks | ||
|
|
|
|
| number of |
| pv_summary |
| valid | meaning | |
| value | ||
| devices |
| |
|
|
| |
|
|
|
|
| 10 | all PVs and data accessible | UP |
|
|
|
|
| 9 | 1 PV down, all data accessible | PVG_UP |
|
|
|
|
| if 5 PVs are from the same PVG, then all data is available | PVG_UP | |
|
|
|
|
|
| if 2 or more physical volumes from different PVGs are DOWN, | SUSPECT |
|
| the disk monitor cannot conclude that all data is available |
|
|
|
|
|
| some data missing |
| |
|
|
| DOWN |
| 0 | no data available | |
|
|
|
|
Resources to Monitor for Lock Disks
Lock disks are used as a
Resource
Monitoring Parameters
Notify | Condition | Option |
/vg/vg02/pv_pvlink/c0t0d1
when value is
>=
BUSY
RETURN
The Repeat value in the Options will send an alert until the lock disk is available.
You need to create a request on each node in the cluster. Because the bus name and SCSI path to the lock disk may be different on each node, the resource instance may have a different name. It is merely a different path to the same lock disk.
Chapter 2 | 55 |