Node2: # dlm_tool ls dlm lockspaces name VMStorage3 id 0xb26438a2 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 1,1 members 1 2 name VMStorage2 id 0xab7f09e3 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 1,1 members 1 2 name VMStorage1 id 0x80525a20 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 1,1 members 1 2 =========================================== Node1: # dlm_tool ls dlm lockspaces name VMStorage3 id 0xb26438a2 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 2,2 members 1 2 name VMStorage2 id 0xab7f09e3 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 2,2 members 1 2 name VMStorage1 id 0x80525a20 flags 0x00000008 fs_reg change member 2 joined 1 remove 0 failed 0 seq 2,2 members 1 2 On Thu, Jan 29, 2015 at 8:57 AM, Digimer <lists@xxxxxxxxxx> wrote: > On 28/01/15 11:50 PM, cluster lab wrote: >> >> Hi, >> >> In a two node cluster, i received to different result from "qemu-img >> check" on just one file: >> >> node1 # qemu-img check VMStorage/x.qcow2 >> No errors were found on the image. >> >> Node2 # qemu-img check VMStorage/x.qcow2 >> qemu-img: Could not open 'VMStorage/x.qcow2" >> >> All other files are OK, and the cluster works properly. >> What is the problem? >> >> ==== >> Packages: >> kernel: 2.6.32-431.5.1.el6.x86_64 >> GFS2: gfs2-utils-3.0.12.1-23.el6.x86_64 >> corosync: corosync-1.4.1-17.el6.x86_64 >> >> Best Regards > > > What does 'dlm_tool ls' show? > > -- > Digimer > Papers and Projects: https://alteeve.ca/w/ > What if the cure for cancer is trapped in the mind of a person without > access to education? > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
