very interesting, I reproduced this issue with 2.03.05-11.1. from the lvm2 rpm change log, and comparing with 2.03.05-8.1, I can't find any patch can introduce this issue.