[Bugs] [Bug 1304976] Glusterfs :sync lost between two boards

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1304976



--- Comment #4 from xinsong <songxin_1980 at 126.com> ---
Hi,
>From the log in board 10.32.0.48 I found the following things. 

[2016-01-30 04:29:07.271245] E [MSGID: 106116]
[glusterd-mgmt.c:134:gd_mgmt_v3_collate_errors] 0-management: Locking failed on
10.32.1.144. Please check log file for details. 
[2016-01-30 04:29:07.271358] E [MSGID: 106151]
[glusterd-syncop.c:1861:gd_sync_task_begin] 0-management: Locking Peers Failed. 
... 

At this point the 10.32.0.48 has lock the volume c_glusterfs successfully, but
failed when it lock the 10.32.1.144.I think it may be because the 10.32.0.48
want to lock twice 10.32.1.144.The reason is because there are same host twice
as below. 

Number of Peers: 2 

Hostname: 10.32.1.144 
Uuid: bbe2a458-ad3d-406d-b233-b6027c12174e 
State: Peer in Cluster (Connected) 

Hostname: 10.32.1.144 
Uuid: bbe2a458-ad3d-406d-b233-b6027c12174e 
State: Peer in Cluster (Connected) 


And the 10.32.0.48 didn't release the volume c_glusterfs lock until 04:39:16 as
below. 
... 
[2016-01-30 04:39:16.976206] E [MSGID: 106116]
[glusterd-mgmt.c:134:gd_mgmt_v3_collate_errors] 0-management: Unlocking failed
on 10.32.1.144. Please check log file for details. 
[2016-01-30 04:39:16.976292] E [MSGID: 106152]
[glusterd-syncop.c:1562:gd_unlock_op_phase] 0-management: Failed to unlock on
some peer(s) 
... 

>From 04:29:07 to 04:39:16 ，the command “add brick” try to lock volume
c_glusterfs lock， but it failed because the lock hasn't been released. 

But I don't understand why the 10.32.0.48 has two peers which are both
10.32.1.144. 

Who can help me to answer my quesion?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=koDh6N5FBX&a=cc_unsubscribe