<div dir="ltr"><div>Hi Toby,<br><br></div>What's the bug #? I want to have a look and backport it to our production server if it helps. Thank you.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/9 Toby Corkindale <span dir="ltr"><<a href="mailto:toby.corkindale@strategicdata.com.au" target="_blank">toby.corkindale@strategicdata.com.au</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 09/07/13 15:38, Bobby Jacob wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Hi,<br>
<br>
I have a 2-node gluster with 3 TB storage.<br>
<br></div>
1)I believe the “glusterfsd” is responsible for the self healing between<br>
the 2 nodes.<br>
<br>
2)Due to some network error, the replication stopped for some reason but<div class="im"><br>
the application was accessing the data from node1. When I manually try<br>
to start “glusterfsd” service, its not starting.<br>
<br>
Please advice on how I can maintain the integrity of the data so that we<br>
have all the data in both the locations. ??<br>
</div></blockquote>
<br>
There were some bugs in the self-heal daemon present in 3.3.0 and 3.3.1. Our systems see the SHD crash out with segfaults quite often, and it does not recover.<br>
<br>
I reported this bug a long time ago, and it was fixed in trunk relatively quickly -- however version 3.3.2 has still not been released, despite the fix being found six months ago.<br>
<br>
I find this quite disappointing.<br>
<br>
T<br>
______________________________<u></u>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>users</a></blockquote></div><br><br clear="all"><br>-- <br>·ûÓÀÌÎ
</div>