As I understand LVM, for mirrored disks (like rootvg below), only 1016 PP's
are tracked for tracking mirror 'staleness'. However, in the rootvg example
below, even though there are more than 1016 PPs in the physical volume, only
622 are actually used. Since what's used is less than 1016, will the LVM
still be able to reliably track PP 'staleness' (until I actually allocate
*over* 1016 of these PPs)?

VOLUME GROUP: rootvg VG IDENTIFIER: 000ac8bf19603fe8
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1084 (34688
megabytes)
MAX LVs: 256 FREE PPs: 462 (14784
megabytes)
LVs: 9 USED PPs: 622 (19904
megabytes)
OPEN LVs: 8 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32

Likewise, the datavg volume group is not mirrored, but is a RAID5 array off
a RAID5 hardware controller. Since this is not mirrored, is the 1016 PP
limitation violation below still a potential problem?
If so, what would the symptoms be, as there's no mirror to go 'stale'.

VOLUME GROUP: datavg VG IDENTIFIER: 000ac8bf7362eadb
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1084 (138752
megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 4 USED PPs: 1084 (138752
megabytes)
OPEN LVs: 4 QUORUM: 2
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32

Thanks for the clarification.
Ken