On 10/04/2013 12:54 AM, Gianluca Cecchi wrote:
On messages of vdsm hosts
Oct 3 23:05:57 f18ovn03 sanlock[1146]: 2013-10-03 23:05:57+0200 16624
[13543]: read_sectors delta_leader offset 512 rv
-5
On Fri, Oct 4, 2013 at 11:30 AM, Itamar Heim wrote:
do you happen to know why it got into a split brain status?
I suppose with the fist migration attempt.
But last night I replicated but I only got the heal for ids file, that
gluster apparently solved itself.
Possibly the bug about ide can
One engine with f19 and two nodes with f19.
All with ovirt stable repo for f19.
DC defined as GlusterFS
The volume is ok, but I can't activate the domain.
Relevant logs when I clich activate are below
On engine:
2013-10-03 23:05:10,332 INFO
On messages of vdsm hosts
Oct 3 23:05:57 f18ovn03 sanlock[1146]: 2013-10-03 23:05:57+0200 16624
[13543]: read_sectors delta_leader offset 512 rv
-5
/rhev/data-center/mnt/glusterSD/f18ovn01.mydomain:gvdata/d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/dom_md/ids
Oct 3 23:05:58 f18ovn03 sanlock[1146]:
And in fact after solving the split brain, the gluster domain
automatically activated.
From rhev-data-center-mnt-glusterSD-f18ovn01.mydomain:gvdata.log under
/var/log/glusterfs I found ids file was the one not in sync
As the VM only started on f18ovn03 and I was not able to migrate to
f18ovn01, I
5 matches
Mail list logo
