Hide Forgot
Description of problem: I was under the impression (possibly falsely) that we weren't going to support the cluster conversion of thinp type volumes. SCENARIO - [convert_snap_to_cluster] Making origin volume Creating thinpool and corresponding thin virtual volumes (one to be used as an origin) lvcreate --thinpool POOL -L 1G snapper_thinp lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n origin lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n other1 lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n other2 lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n other3 lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n other4 lvcreate --virtualsize 1G --thinpool snapper_thinp/POOL -n other5 Create a snap and then rename it lvcreate -s /dev/snapper_thinp/origin -n to_cluster Exclusively lock the VG, and then attempt to convert to a clustered VG vgchange -aye snapper_thinp vgchange -c y snapper_thinp lvm shouldn't allow VGs containing snapshots to become clustered Version-Release number of selected component (if applicable): 2.6.32-348.el6.x86_64 lvm2-2.02.98-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 lvm2-libs-2.02.98-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 lvm2-cluster-2.02.98-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 udev-147-2.43.el6 BUILT: Thu Oct 11 05:59:38 CDT 2012 device-mapper-1.02.77-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 device-mapper-libs-1.02.77-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 device-mapper-event-1.02.77-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 device-mapper-event-libs-1.02.77-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 cmirror-2.02.98-5.el6 BUILT: Wed Dec 12 09:18:07 CST 2012 How reproducible: Everytime
Thin volumes are supported in cluster - however only on 'exclusive' activation mode - so only one node is able to activate thin pool and all related thin volumes. No other cluster node should be then allowed to active such pool and their volumes.