Hi, i´ve narrowed down the problem to something similar if not the same as posted recently on this list. It seems that the problem lies within the LV creation. My systemis using RHEL 5.1 and when i´ve manually create a LV i´ve received was something like Error locking on node node1 Volume group for uuid not found: 0PfAdiZHlULoLDX3gw3OGFrwsbPS8io1SWPEFXXOI0VzhYJLy8nGpBFdT7Oi25bF Failed to activate new LV. but the LV appearead on the creation node and after a while (several reboots) in the another node. That leads me to think that my gfs2 problem lies there. I´ve upgraded to RHEL 5.2 in order to use the lvm2 and kernel upgraded packages that seemed to solve similar issues. However, the error changed a bit as well as the behaviour at the LV creation. When i execute the lvcreate command i get this error lvcreate -n ems_lv -L +5.99G ems_vg Rounding up size to full physical extent 5.99 GB Error locking on node ems88clu2.bvc.com.co: Error backing up metadata, can't find VG for group #global Aborting. Failed to activate new LV to wipe the start of it. the difference with 5.1 is that previously the lv was created only at the creation node , with 5.2 besides the different error message the LV is NOT created at either both nodes. This is happening inside a guest accessing the san as a virtual block device presented by the domain-0 (the domain-o exports the mpath device). The nodes are in different domain-0 accessing the same SAN Thanks for your help -- Andrés Mauricio Mujica Zalamea -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
