[Gluster-users] Errors on mounting (but works)

[Martin Lindkvist]

Hi!

When I'm mounting a client with fstab and a server-supplied client-spec file
I get the following in the server-log:

2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (63) for new transport object of 192.168.10.12
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)
2008-09-15 15:04:42 E [protocol.c:271:gf_block_unserialize_transport]
server: EOF from peer (192.168.10.12:1023)
2008-09-15 15:04:42 D [tcp.c:87:tcp_disconnect] server: connection
disconnected
2008-09-15 15:04:42 D [server-protocol.c:6262:server_protocol_cleanup]
server: cleaned up transport state for client 192.168.10.12:1023
2008-09-15 15:04:42 D [tcp-server.c:257:gf_transport_fini] server:
destroying transport object for 192.168.10.12:1023 (fd=63)
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (63) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce1: allowed = "*", received
ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:1022
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (66) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce2: allowed = "*", received
ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:1010
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (67) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] mapreduce-namespace: allowed = "*",
received ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:1002
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (68) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] www1: allowed = "*", received ip
addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:981
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (69) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] www2: allowed = "*", received ip
addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:976
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (70) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] www-namespace: allowed = "*",
received ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:975
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (71) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] home1: allowed = "*", received ip
addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:972
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (72) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] home2: allowed = "*", received ip
addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:967
2008-09-15 15:04:42 D [tcp-server.c:145:tcp_server_notify] server:
Registering socket (73) for new transport object of 192.168.10.12
2008-09-15 15:04:42 D [ip.c:120:gf_auth] home-namespace: allowed = "*",
received ip addr = "192.168.10.12"
2008-09-15 15:04:42 D [server-protocol.c:5667:mop_setvolume] server:
accepted client from 192.168.10.12:966


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?

The client-spec file is specified in the server-spec file like this:
   option client-volume-filename /etc/glusterfs/glusterfs-client.vol

The line in /etc/fstab looks like this:
  192.168.10.30   /srv/mapreduce        glusterfs
auto,volume-name=mapreduce 0       0

Everything seems to work just fine though. But the errors in the log are
disturbing.

/Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20080915/a68b39ae/attachment.html>