<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 4, 2018 at 4:13 AM, Serg Gulko <span dir="ltr"><<a href="mailto:s.gulko@gmail.com" target="_blank">s.gulko@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello! </div><div><br></div><div>We are running distributed volume that contains 7 bricks. </div><div>Volume is mounted using native fuse client. </div><div><br></div><div>After an unexpected system reboot, some files are disappeared from fuse mount point but still available on the bricks. </div><div><br></div><div>The way it disappeared confusing me a lot. I can't see certain directories using ls -la but, at the same time, can cd into the missed directory. I can rename the invisible directory and it becomes accessible. When I renamed it back to the original name, it becomes invisible. </div><div><br></div><div>I also tried to mount the same volume into another location and run ls hoping that selfheal will fix the problem. Unfortunately, it did not. </div><div><br></div><div>Is there a way to bring our storage to normal?</div></div></blockquote><div><br></div><div>Can you check whether turning off option performance.readdir-ahead helps?</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>glusterfs 3.8.8 built on Jan 11 2017 16:33:17</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Serg Gulko </div></font></span></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div></div>