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. In addition the error message was unhelpful: -bash-3.2# glusterfs --server fs01 /data --volume-name=data glusterfs: could not open specfile -- Matt
Why not change the perms on the mount-point? On Sat, 2008-11-22 at 16:35 -0600, Matt Lawrence wrote:> 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. > > In addition the error message was unhelpful: > > -bash-3.2# glusterfs --server fs01 /data --volume-name=data > glusterfs: could not open specfile > > -- Matt
Hi Matt, Is the volume specfication file present on the server? The default path is <CONFDIR>/glusterfs.vol. This is overridden by the path given in client-volume-filename option in server configuration. regards, On Sun, Nov 23, 2008 at 2:35 AM, Matt Lawrence <matt.lawrence at tamu.edu>wrote:> 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. > > In addition the error message was unhelpful: > > -bash-3.2# glusterfs --server fs01 /data --volume-name=data > glusterfs: could not open specfile > > -- Matt > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users >-- Raghavendra G -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081124/aac27238/attachment.html>
Raghavendra G wrote:> Hi Matt, > > Is the volume specfication file present on the server? The default > path is <CONFDIR>/glusterfs.vol. This is overridden by the path given > in client-volume-filename option in server configuration.Yes, it is. All I needed to do to make it work was to delete the files that had been created under the mount point. -- Matt
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://supercolony.gluster.org/pipermail/gluster-users/attachments/20081125/6eac0f7c/attachment.html>