<div dir="ltr">Hi!<br><br>When I'm mounting a client with fstab and a server-supplied client-spec file I get the following in the server-log:<br><br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (63) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 E [server-protocol.c:5212:mop_getspec] server: Unable to open /etc/glusterfs/glusterfs-client.vol.192.168.10.12 (No such file or directory)<br>2008-09-15 15:04:42 E [protocol.c:271:gf_block_unserialize_transport] server: EOF from peer (<a href="http://192.168.10.12:1023">192.168.10.12:1023</a>)<br>
2008-09-15 15:04:42 D [tcp.c:87:tcp_disconnect] server: connection disconnected<br>2008-09-15 15:04:42 D [server-protocol.c:6262:server_protocol_cleanup] server: cleaned up transport state for client <a href="http://192.168.10.12:1023">192.168.10.12:1023</a><br>
2008-09-15 15:04:42 D [tcp-server.c:257:gf_transport_fini] server: destroying transport object for <a href="http://192.168.10.12:1023">192.168.10.12:1023</a> (fd=63)<br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (63) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce1: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:1022">192.168.10.12:1022</a><br>
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (66) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce2: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:1010">192.168.10.12:1010</a><br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (67) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce-namespace: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:1002">192.168.10.12:1002</a><br>
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (68) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>2008-09-15 15:04:42 D [ip.c:120:gf_auth] www1: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:981">192.168.10.12:981</a><br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (69) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 D [ip.c:120:gf_auth] www2: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:976">192.168.10.12:976</a><br>
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (70) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>2008-09-15 15:04:42 D [ip.c:120:gf_auth] www-namespace: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:975">192.168.10.12:975</a><br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (71) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 D [ip.c:120:gf_auth] home1: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:972">192.168.10.12:972</a><br>
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (72) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>2008-09-15 15:04:42 D [ip.c:120:gf_auth] home2: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:967">192.168.10.12:967</a><br>2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server: Registering socket (73) for new transport object of <a href="http://192.168.10.12">192.168.10.12</a><br>
2008-09-15 15:04:42 D [ip.c:120:gf_auth] home-namespace: allowed = "*", received ip addr = "<a href="http://192.168.10.12">192.168.10.12</a>"<br>2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server: accepted client from <a href="http://192.168.10.12:966">192.168.10.12:966</a><br>
<br><br>There is no /etc/glusterfs/glusterfs-client.vol.192.168.10.12, the client-spec-file is named /etc/glusterfs/glusterfs-client.vol, does gluster automatically assume that the file is ending with the client's ip?<br>
<br>The client-spec file is specified in the server-spec file like this:<br> option client-volume-filename /etc/glusterfs/glusterfs-client.vol<br><br>The line in /etc/fstab looks like this:<br> <a href="http://192.168.10.30">192.168.10.30</a> /srv/mapreduce glusterfs auto,volume-name=mapreduce 0 0<br>
<br>Everything seems to work just fine though. But the errors in the log are disturbing.<br><br>/Martin<br><br></div>