Actually, even on another Linux machine mounting NFS has the same behaviour. I am able to mount it with “mount –t nfs …” but when I try “ls” it hangs as well. One particular thing of the Gluster servers is that they have two networks, one for management with default gateway and another only for storage. I am only able to mount on the storage network. The hosts file has all nodes’ names with the ips on the storage network. I tried to use this but didn’t work either. gluster volume set VOLUME nfs.rpc-auth-allow 10.10.100.* Watching the nfs logs when I try a “ls” from the remote client it shows: pending frames: patchset: git://git.gluster.com/glusterfs.git signal received: 11 time of crash: 2012-05-25 11:38:09 configuration details: argp 1 backtrace 1 dlfcn 1 fdatasync 1 libpthread 1 llistxattr 1 setfsid 1 spinlock 1 epoll.h 1 xattr.h 1 st_atim.tv_nsec 1 package-string: glusterfs 3.3.0beta4 /lib64/libc.so.6(+0x32900)[0x7f1c92d92900] /usr/lib64/glusterfs/3.3.0beta4/xlator/cluster/replicate.so(afr_lookup+0xa5)[0x7f1c8e7a6ac5] /usr/lib64/glusterfs/3.3.0beta4/xlator/cluster/stripe.so(stripe_readdirp_cbk+0x536)[0x7f1c8e543346] /usr/lib64/glusterfs/3.3.0beta4/xlator/cluster/replicate.so(afr_readdirp_cbk+0x1ca)[0x7f1c8e76269a] /usr/lib64/glusterfs/3.3.0beta4/xlator/protocol/client.so(client3_1_readdirp_cbk+0x170)[0x7f1c8e9dbbe0] /usr/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0xa2)[0x7f1c9388b302] /usr/lib64/libgfrpc.so.0(rpc_clnt_notify+0xb6)[0x7f1c9388b516] /usr/lib64/libgfrpc.so.0(rpc_transport_notify+0x27)[0x7f1c93886e17] /usr/lib64/glusterfs/3.3.0beta4/rpc-transport/socket.so(socket_event_poll_in+0x3f)[0x7f1c8f818c8f] /usr/lib64/glusterfs/3.3.0beta4/rpc-transport/socket.so(socket_event_handler+0x188)[0x7f1c8f818e38] /usr/lib64/libglusterfs.so.0(+0x3eb51)[0x7f1c93ad0b51] /usr/sbin/glusterfs(main+0x502)[0x406612] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f1c92d7ecdd] /usr/sbin/glusterfs[0x404399] Thanks
From: Fernando
Frediani (Qube) Hi, I’ve setup a Gluster environment using CentOS 6.2 and GlusterFS 3.3 beta4 and the new type of volume striped + replicated. My go is to use it to run Virtual Machines (.vmdk files). Volume is created fine and the ESXi server mountw the Datastore using Gluster built-in NFS, however when trying to use the Datastore or even read, it hangs. Looking at the Gluster NFS logs I see: “[socket.c:195:__socket_rwv] 0-socket.nfs-server: readv failed (Connection reset by peer)” In order to get the rpm files installed I had first to install these two because of the some libraries: “compat-readline5-5.2-17.1.el6.x86_64”.rpm and “openssl098e-0.9.8e-17.el6.centos.x86_64.rpm”.Not
sure if it has anything to do with that. Has anyone ever used Gluster as a backend storage for ESXi ? Does it actually work ? Regards, Fernando Frediani Qube Managed Services Limited sales: +44 (0) 20 7150 3800 P
Please consider the environment before printing this email |