Thanks Vikas, but how does it know that it's the first access for the file? Also what happens when somehow a file got deleted or corrupted on one of the servers? At what point will gluster replicate that file again?<div>
<br></div><div>Alex<br><div><br></div><div>how does it know<br><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 12:56 AM, Vikas Gorur <span dir="ltr"><<a href="mailto:vikas@gluster.com">vikas@gluster.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Alex Attarian wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'll give that a try Gordan! Thanks for the info! <br>
My other question is does gluster perform a read for the extended attributes on all servers regardless read-subvolume?<br>
This is what my tcpdump shows:<br>
</blockquote></div>
[snip]<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Does it have to read the trusted.afr.* attributes from every server every time it reads a file?<br>
</blockquote></div>
Yes, the extended attributes are read from all servers on the first access to the file (i.e., lookup).<br>
It is not done on every read ().<br>
<br>
As Gordon said, this is done to gather the metadata needed to decide whether a self-heal<br>
needs to be done.<br>
<br>
Vikas<br><font color="#888888">
--<br>
Engineer - Gluster, Inc.<br>
</font></blockquote></div><br></div></div>