I am having problems mounting glusterfs filesystems inside of vservers. It appears that perhaps the secure-mount utility cannot handle them? I tried adding an entry to the /etc/vserver/<vname>/fstab like this: 10.10.20.11 /data/unpublished glusterfs defaults 0 0 and it does not work. The vserver starts up but if I try to ls /data/unpublished in the vserver the ls command locks up. The same entry in the hosts fstab works fine. Using the secure-mount command I have similar results, I tried: secure-mount -t glusterfs 10.10.20.11 data/unpublished from the vserver root (non chrooted) and it locks up. I tried it with strace and I get: execve("/usr/lib/util-vserver/secure-mount", ["/usr/lib/util-vserver/secure-mou" ublished"], [/* 16 vars */]) = 0 open(".", O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 3 open("/", O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 4 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0 chdir("data/unpublished") = 0 open(".", O_RDONLY|O_LARGEFILE|O_DIRECTORY That didn't seem very helpful. However, I was able to mount the share with: vnamespace -e 62 mount.glusterfs 10.10.20.11 /<vserver_root>/data/unpublished Any thoughts on what could be wrong? -Martin Debian kernel: 2.6.17-1-vserver-686 util-vserver: 0.30.216~r2750-3 glusterfs: 1.3.10-1 (glusterfs--mainline--2.5--patch-788)