Bug 765318 (GLUSTER-3586) - cannot fetch volume files with transport type rdma
Summary: cannot fetch volume files with transport type rdma
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3586
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-19 12:13 UTC by Raghavendra G
Modified: 2011-09-21 13:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Raghavendra G 2011-09-19 12:13:07 UTC 
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 05:14:52 UTC 
CHANGE: http://review.gluster.com/475 (Change-Id: Ie52e4b1a338282f2697e2ce374dd566d2c5cf5d1) merged in master by Vijay Bellur (vijay)
Note You need to log in before you can comment on or make changes to this bug.