I just had to deal with a situation where a glusterfs filesystem would > not mount because someone had managed to create some files and > directories under the mount point. Perhaps this behavior is > intentional, but I would prefer that it work like NFS and just > overmount. When bringing a cluster down and back up, it is quite > possible for overeager users to log in and start working before > everything is up. That is how it is. It does overmount on existing files/directories under the requested mount point. Which version of glusterfs are you using? > In addition the error message was unhelpful: > > -bash-3.2# glusterfs --server fs01 /data --volume-name=data > glusterfs: could not open specfile > Is there any hint in the server log file? avati -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081125/6eac0f7c/attachment.htm
