Hi,<br><br><div class="gmail_quote">On Sat, Nov 15, 2008 at 1:03 AM, KwangErn Liew <span dir="ltr"><<a href="mailto:ke.liew@gmail.com">ke.liew@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Nov 14, 2008 at 12:05 PM, Vikas Gorur <span dir="ltr"><<a href="mailto:vikas@zresearch.com" target="_blank">vikas@zresearch.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/11/14 Onyx <<a href="mailto:lists@bmail.be" target="_blank">lists@bmail.be</a>>:<br>
<div>> Hi,<br>
><br>
> I just had a problem with a disk failure. It was an ext3 partition, and<br>
> suddenly, bc of a problem, it automatically remounted as read-only.<br>
> It was not in a glusterfs setup yet, but it got me thinking...<br>
> What would have happened if that partition was in an afr setup?<br>
> I think glusterfs would hang on a write, correct?<br>
<br>
</div>No, AFR would not hang. The write would fail on that volume, but as long<br>
as the write succeeds on atleast one volume, AFR reports success.<br>
</blockquote></div><br></div>Is there N tries before write is reported to be failed on that volume? Or is it failed immediately?</blockquote><div><br>There are no retries. It is failed immediately.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font color="#888888"><br><br>KwangErn<br>
</font><br>_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>