OK. This is a bug in LVM2 that is fixed in the re1213.0 tree, bug 142977.
lvm2-2.00.31-1.0.RHEL4.i386.rpm should fix this problem. I'm checking to see
when/where this update will be pushed to partners.