<br><div class="gmail_quote"><span dir="ltr"></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I just had to deal with a situation where a glusterfs filesystem would<br>
not mount because someone had managed to create some files and<br>
directories under the mount point. Perhaps this behavior is<br>
intentional, but I would prefer that it work like NFS and just<br>
overmount. When bringing a cluster down and back up, it is quite<br>
possible for overeager users to log in and start working before<br>
everything is up.</blockquote><div><br><br>That is how it is. It does overmount on existing files/directories under the requested mount point. Which version of glusterfs are you using?<br><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>
In addition the error message was unhelpful:<br>
<br>
-bash-3.2# glusterfs --server fs01 /data --volume-name=data<br>
glusterfs: could not open specfile<br>
</blockquote><div><br>Is there any hint in the server log file? <br><br>avati<br></div></div><br>