<div dir="ltr"><div>Hi. <br></div><div><br></div><div>I have a some question about your testing.</div><div><br></div><div>1. What was the glusterfs version you used in past time?</div><div>2. How about a volume configuration?</div><div>3. Was CTDB vip failed over correctly? If so, Clould you attach /var/log/samba/glusterfs-volname.win10.ip.log ?</div><div><br></div><div>Best Regards</div><div><br></div><div>- kpkim<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2019년 4월 17일 (수) 오후 5:02, David Spisla <<a href="mailto:spisla80@gmail.com">spisla80@gmail.com</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Dear Gluster Community,</div><div><br></div><div>I have this setup: 4-Node Glusterfs v5.5 Cluster, using SAMBA/CTDB v4.8 to access the volumes (each node has a VIP)<br></div><div><br></div><div>I was testing this failover scenario:</div><div><br></div><div>1. Start Writing
<span style="font-size:11pt;font-family:"Calibri",sans-serif">940 GB with small files (64K-100K)from a Win10 Client to node1<br></span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif">2. During the write process I hardly shutdown node1
<span style="font-size:11pt;font-family:"Calibri",sans-serif">(where the client is connect via VIP)</span>
by turn off the power <br></span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif"><br></span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif">My expectation is, that the write process stops and after a while the Win10 Client offers me a Retry, so I can continue the write on different node (which has now the VIP of node1).</span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif">In past time I did this observation, but now the system shows a strange bahaviour:</span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif"><br></span></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif">The Win10 Client do nothing and the Explorer freezes, in the backend CTDB can not perform the failover and throws errors. The glusterd from node2 and node3 logs this messages:</span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><span style="font-size:11pt;font-family:"Calibri",sans-serif">
</span><pre class="gmail-m_6256914356656820661gmail-code-java">[2019-04-16 14:47:31.828323] W [glusterd-locks.c:795:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x24349) [0x7f1a62fcb349] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x2d950) [0x7f1a62fd4950] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0xe0359) [0x7f1a63087359] ) 0-management: Lock <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> vol archive1 not held
[2019-04-16 14:47:31.828350] W [MSGID: 106117] [glusterd-handler.c:6451:__glusterd_peer_rpc_notify] 0-management: Lock not released <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> archive1
[2019-04-16 14:47:31.828369] W [glusterd-locks.c:795:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x24349) [0x7f1a62fcb349] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x2d950) [0x7f1a62fd4950] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0xe0359) [0x7f1a63087359] ) 0-management: Lock <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> vol archive2 not held
[2019-04-16 14:47:31.828376] W [MSGID: 106117] [glusterd-handler.c:6451:__glusterd_peer_rpc_notify] 0-management: Lock not released <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> archive2
[2019-04-16 14:47:31.828412] W [glusterd-locks.c:795:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x24349) [0x7f1a62fcb349] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0x2d950) [0x7f1a62fd4950] -->/usr/lib64/glusterfs/5.5/xlator/mgmt/glusterd.so(+0xe0359) [0x7f1a63087359] ) 0-management: Lock <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> vol gluster_shared_storage not held
[2019-04-16 14:47:31.828423] W [MSGID: 106117] [glusterd-handler.c:6451:__glusterd_peer_rpc_notify] 0-management: Lock not released <span class="gmail-m_6256914356656820661gmail-code-keyword">for</span> gluster_shared_storage</pre>
</div></blockquote><div> </div><div><b>In my oponion Samba/CTDB can not perform the failover correctly and continue the write process because glusterfs didn't released the lock.</b> What do you think? It seems to me like a bug because in past time the failover works correctly.</div><div><br></div><div>Regards</div><div>David Spisla<br></div><div><span style="font-size:11pt;font-family:"Calibri",sans-serif"><br></span>
</div></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>