Ok, i made some progresses. First, i can propagate the device mapper configuration for the created snapshot 'lv_snap2' on other nodes by executing: 1) lvscan 2) lvchange --refresh vg_local Last command returns these messages: --- _get_device_info: device not found _get_device_info: device not found vg_local/snapshot1: snapshot segment monitoring function failed. --- However the device mapper configurations seems ok, because the command 'dmsetup table' shows entries related to 'lv_snap2'. Then, i removed the snapshot from the node that created it and i tried to propagate the change on another node by executing same commands above. The command lvchange reports this message: --- Unable to deactivate open vg_local-lv_origin (253:5) --- and the device mapper configuration is not changed. How i can remove device mapper entries on other nodes? Thanks Roberto Sassu On Thursday, January 06, 2011 11:34:50 am Roberto Sassu wrote: > Hi Ray > > On Wednesday, January 05, 2011 09:53:33 pm Ray Morris wrote: > > What says lvscan -vv ? > > lvscan tells the 'Original' LV is inactive, 'lv_snap1' is active, > 'lv_snap2' is inactive. > Executing 'lvchange -ay lv_origin' does not change the status > of 'lv_snap2'. > If i run the command 'vgchange -ay' without 'vgchange -an', > i get this error message: > > _get_device_info: device not found > > > Thanks > > Roberto Sassu > > > > -- > > Ray Morris > > support@bettercgi.com > > > > Strongbox - The next generation in site security: > > http://www.bettercgi.com/strongbox/ > > > > Throttlebox - Intelligent Bandwidth Control > > http://www.bettercgi.com/throttlebox/ > > > > Strongbox / Throttlebox affiliate program: > > http://www.bettercgi.com/affiliates/user/register.php > > > > On 01/05/2011 11:48:54 AM, Roberto Sassu wrote: > > > Hi all > > > > > > i configured a LVM volume group using two iSCSI devices as > > > physical volumes. > > > I designed one node (A) to create snapshots of a Logical Volume, > > > called 'lv_origin' and i want other nodes (B, C) access them > > > exclusively. > > > I assume that 'lv_origin' is never modified after the first snapshot > > > is created. > > > So, A first creates 'lv_origin' and then a snapshot called > > > 'lv_snap1', which is available for this node. > > > The node B executes the command 'vgscan' and 'vgchange -ay'. > > > In this way, 'lv_origin' and 'lv_snap1' become available for B. > > > Next step, A creates a new snapshot of 'lv_origin' called > > > 'lv_snap2'. This is not available for B and the only way that i > > > found to use it is to perform (on the node B) the following > > > commands: > > > > > > 1) vgscan > > > 2) vgchange -an > > > 3) vgchange -ay > > > > > > However this procedure is not applicable if one of created > > > LVs is in use. How to solve this issue? > > > > > > Thanks in advance for replies > > > > > > Roberto Sassu > > > > > > _______________________________________________ > > > linux-lvm mailing list > > > linux-lvm@redhat.com > > > https://www.redhat.com/mailman/listinfo/linux-lvm > > > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > > > > _______________________________________________ > > linux-lvm mailing list > > linux-lvm@redhat.com > > https://www.redhat.com/mailman/listinfo/linux-lvm > > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
