Hello, I tried to NFS-mount a gluster-volume using the "normal NFS-way" with the directory-path: mount -t nfs 192.168.1.88:/raid/nfstest /mnt/testmount This gives me only the following error message: mount.nfs: mounting 192.168.1.88:/raid/nfstest failed, reason given by server: No such file or directory But if I understand the information given here correct, (http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_NFS_Frequently_Asked_Questions#How_to_export_directories_as_separate_NFS_exports.3F) it should be possible to mount the NFS exports like mentioned above...? The nfs.log looks like the correct options are set in the configuration... 1: volume test-nfs-client-0 2: type protocol/client 3: option remote-host 192.168.1.88 4: option remote-subvolume /raid/nfstest 5: option transport-type tcp 6: end-volume 7: 8: volume test-nfs-write-behind 9: type performance/write-behind 10: subvolumes test-nfs-client-0 11: end-volume 12: 13: volume test-nfs-read-ahead 14: type performance/read-ahead 15: subvolumes test-nfs-write-behind 16: end-volume 17: 18: volume test-nfs-io-cache 19: type performance/io-cache 20: subvolumes test-nfs-read-ahead 21: end-volume 22: 23: volume test-nfs-quick-read 24: type performance/quick-read 25: subvolumes test-nfs-io-cache 26: end-volume 27: 28: volume test-nfs 29: type debug/io-stats 30: subvolumes test-nfs-quick-read 31: end-volume 32: 33: volume nfs-server 34: type nfs/server 35: option nfs.dynamic-volumes on 36: option rpc-auth.addr.test-nfs.allow * 37: option nfs3.test-nfs.volume-id 7658e857-8fc0-4cac-a1ca-1882329b6fc2 38: subvolumes test-nfs 39: end-volume Is this a bug in gluster, or am I missing something here? Mounting the Gluster-volume with the volume-name over NFS works... (mount -t nfs 192.168.1.88:/test-nfs /mnt/testmount) Kind regards, Thomas
