Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Administering a System: Managing Disks and Files
Managing Disks
Chapter 6568
As of HP-UX 11i version 2, LVM no longer performs bad block relocation
in software, but defers to the hardware bad block relocation implemented
within modern disks and disk arrays. LVM recognizes and honors
software relocation entries created by previous releases, but will not
create new ones. Enabling or disabling bad block relocation via lvchange
has no effect.
The -r option of lvcreate cannot be used with HP-IB devices.
Increasing Availability with Alternate Links
Your hardware may provide the capability for dual cabling (dual
controllers) to the same physical volume. This will be true if your
organization has purchased an HP High Availability Disk Array or the
MC/ServiceGuard product. If so, LVM can be configured with multiple
paths to the same physical volume. If the primary link fails, an
automatic switch to an alternate link will occur. Using alternate links
will increase availability. See “Setting Up Alternate Links to a Physical
Volume” on page 587.
LVM Naming Conventions
By default, HP-UX uses certain naming conventions for physical
volumes, volume groups, and logical volumes. You need to refer to LVM
devices or volume groups by name when using them within SAM, with
HP-UX commands, or when viewing information about them.
Naming Physical Volumes
Physical volumes are identified by their device file names, for example:
/dev/dsk/c n t n d n
/dev/dsk/c n t n d n s2
/dev/rdsk/c n t n d n
/dev/rdsk/c n t n d n s2
Note that each disk has a block device file and a character or raw
device file, the latter identified by the r. Which name you use depends on
what task you are doing with the disk. In the notation above, the first
two names represent block device files while the second two are raw
device files.