Comment 2 for bug 726776

I think your right, this might be better solved by adding a small script to the RHCS configuration that looks for the snapshot volume and removes it if found then tries to start up.

However, this bring up another issue: lvm tagging. For this to work you would have to have the ability to set a tag on the snapshot volume when its created. Something like this:

# lvmcreate -L50GB --addtag @12345db1 -n mysql00_snapshop vgsan00

That will allow you to add an exception to the /etc/lvm/lvm.conf volume_list so it can mount up that LV.