<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">The client problem was that, after doing the above to the storage servers, the client(s) obviously had cache issues. Doing an “ls” on a native GlusterFS mount showed only several subdirectories out of many, and a “du –sh” of the mount point gave this message on the client:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> du: fts_read failed: No such file or directory<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Clearing the client cache as suggested did not resolve this problem, but restarting the client (I have my own /etc/init.d/gluster-client script, which basically loads and unloads the gluster-fuse module and does the mounts and dismounts) cleared up the problem.<u></u><u></u></span></p>
<div class="im"><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> </span></p></div></div></div></blockquote><div><br></div><div>Then its not a caching problem. The problem could be in the volume graph, or server exporting volume graph. 3.1.3 clients were not connected to servers perhaps. Please file a bug with relevant logs, we might have to see why there was no successful reconnect. </div>
</div><div><br></div>Regards<br>-- <br><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><pre cols="72"><span style="white-space:normal"><i><pre cols="72" style="text-align:left"><font face="'courier new', monospace">Harsha</font></pre>
<pre cols="72" style="text-align:left"><font face="'courier new', monospace">Gluster Inc</font></pre></i></span></pre></blockquote><br>