HP-UX 11i v3 LVM New Features in HP-UX 11i v3 (September 2009)

14
ot support combination
g and striping is
ed on HP-UX 11i v3, attempts to import or activate its associated volume group fails on a previous HP-UX
To import the volume group with striped and mirrored logical volume to releases prior to HP-UX 11i v3, you must
iped and mirrored logical volume is supported on HP-UX 11i v2 with the PHCO_36744, PHKL_36745
tches or superseding patches installed on a HP-UX 11i v2 system,
volume group with striped and mirrored logical volume created on
HP-UX 11i v3.
Other Disk Users
s. The LVM commands pvcreate and vgcfgrestore now check if their target
nmark a LVM disk. This is facilitated by the
pvremove command. For more
ion, see the pvremove(1M) man page.
the disk, overwriting any other
scripts or during initializing a
command.
isk – If the disk /dev/dsk/c3t1d1 is marked for use by Oracle ASM, an
ngs to some other subsystem as follows:
pvcreate: Could not perform LVM operation on Oracle ASM disk "/dev/rdsk/c3t1d1"
e command as follows:
sk/disk26
removed.
Software bad block relocation refers to capability of LVM to handle I/O errors on disk blocks that are bad. In
previous releases of HP-UX, when a media failure occurs (detection of a bad block of data on disk), LVM marks
the failed block in the Bad Block Directory and attempts to relocate the block to a new location in the Bad Block
Reserve Area(BBRA) on the disk.
The BBRA was created when the disk was initialized using the
pvcreate command.
All modern disks now offer hardware based bad sector relocation and do not trigger the LVM software relocation.
With HP-UX 11i v3, LVM does not reserve a BBRA at the end of disk to allocate more space for user data.
Compatibility Note
Releases prior to HP-UX 11i v3 only support striped or mirrored logical volumes and do n
of striped and mirrored logical volumes. If a logical volume using simultaneous mirrorin
creat
release.
remove the incompatible logical volumes or reduce them to no mirrors.
NOTE: Str
and PHCO_36746 patches. With these pa
you can successfully import and activate a
Better Coexistence with
LVM coexists better with other disk user
device is in use by other subsystems.
LVM has a provision to disown or u
informat
Note:
pvcreate with the force option -f overrides this check and takes ownership of
subsystems data. HP recommends NOT using the
-f option by default in any of your
physical volume using
pvcreate
Example
Coexistence with Oracle ASM d
initialization operation on this disk identifies that the disk belo
# pvcreate /dev/rdsk/c3t1d1
To disown or unmark an LVM disk that is not part of any volume group, use the
pvremov
# pvremove /dev/rdi
The physical volume associated with "/dev/rdisk/disk26" has been
Better Utilization of Disk Space – No Bad Block Reserve Area