Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

Checking for RAID-5 volumes without a RAID-5 log
(vxse_raid5log1)
To check whether a RAID-5 volume has an associated RAID-5 log, run rule
vxse_raid5log1.
In the event of both a system failure and a failure of a disk in a RAID-5 volume,
data that is not involved in an active write could be lost or corrupted if there is
no RAID-5 log.
See “Adding a RAID-5 log” on page 328.
Checking minimum and maximum RAID-5 log sizes
(vxse_raid5log2)
To check that the size of RAID-5 logs falls within the minimum and maximum
recommended sizes, run rule vxse_raid5log2.
The recommended minimum and maximum sizes are 64MB and 1GB respectively.
If vxse_raid5log2 reports that the size of the log is outside these boundaries,
adjust the size by replacing the log.
Checking for non-mirrored RAID-5 logs (vxse_raid5log3)
To check that the RAID-5 log of a large volume is mirrored, run the
vxse_raid5log3 rule.
A mirror of the RAID-5 log protects against loss of data due to the failure of a
single disk. You are strongly advised to mirror the log if vxse_raid5log3 reports
that the log of a large RAID-5 volume does not have a mirror.
See “Adding a RAID-5 log” on page 328.
Disk groups
Disks groups are the basis of VxVM storage configuration so it is critical that the
integrity and resilience of your disk groups are maintained. Storage Expert
provides a number of rules that enable you to check the status of disk groups and
associated objects.
Checking whether a configuration database is too full
(vxse_dg1)
To check whether the disk group configuration database has become too full, run
rule vxse_dg1.
511Using Storage Expert
Identifying configuration problems using Storage Expert