For which operation are you finding EAGAIN when all servers are down? It is probably a wrong errno coming along. You shouldn't need to do anything in the FUSE layer, just send it back to the application.<div><br></div>
<div>Avati<br><br><div class="gmail_quote">On Mon, Jul 23, 2012 at 5:31 AM, Emmanuel Dreyfus <span dir="ltr"><<a href="mailto:manu@netbsd.org" target="_blank">manu@netbsd.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
on release-3.3,when all replicated subvolumes are down, FUSE receive<br>
EAGAIN. Is that the intended behavior? IF it is, then what is the proper<br>
behavior for the FUSE implementation when receiving that? Should the<br>
operation be replayed after a while? (how long?) Or should EAGAIN be<br>
reported to userland? What does Linux?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Emmanuel Dreyfus<br>
<a href="mailto:manu@netbsd.org">manu@netbsd.org</a><br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br>
<a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</font></span></blockquote></div><br></div>