Bug 765318 (GLUSTER-3586)

Summary: cannot fetch volume files with transport type rdma
Product: [Community] GlusterFS Reporter: Raghavendra G <raghavendra>
Component: glusterdAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Raghavendra G 2011-09-19 08:13:07 EDT
The names of the volume file while generating and while accessing volume files for transport rdma are different. Hence glusterd ends up getting ENOENT errors during fetching of volume file from client file.

[root@client4 build]# ls /etc/glusterd/vols/repl-rdma/*fuse*
/etc/glusterd/vols/repl-rdma/repl-rdma.rdma-fuse.vol

And the name it uses to access this file:
[2011-09-19 03:16:52.578812] E [glusterd-handshake.c:143:server_getspec] 0-glusterd: Unable to stat /etc/glusterd/vols/repl-rdma/repl-rdma-tcp.vol (No such file or directory)
[2011-09-19 03:18:11.570255] E [glusterd-handshake.c:143:server_getspec] 0-glusterd: Unable to stat /etc/glusterd/vols/repl-rdma/repl-rdma-tcp.vol (No such file or directory)

regards,
Raghavendra.
Comment 1 Anand Avati 2011-09-21 01:14:52 EDT
CHANGE: http://review.gluster.com/475 (Change-Id: Ie52e4b1a338282f2697e2ce374dd566d2c5cf5d1) merged in master by Vijay Bellur (vijay@gluster.com)