<div class="gmail_quote">BTW, is there someone have configured gluster like HDFS (unify with automatic replication). Could someone share the volfile here?</div><div class="gmail_quote"></div><div class="gmail_quote">I think I'm not the only fan waiting here ;-)</div>
<div class="gmail_quote"></div><div class="gmail_quote">Gnep</div><div class="gmail_quote"></div><div class="gmail_quote"></div><div class="gmail_quote">On Wed, Jul 1, 2009 at 6:39 PM, Peng Zhao <span dir="ltr"><<a href="mailto:blackass@gmail.com">blackass@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>OK, my stupid. There was no fuse module. I built one and modprobe fuse. The previous error is gone, with some new one:<br>
</div><div>Here are the DEBUG-level msg:</div><div>[2009-07-01 18:36:25] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /usr/lib64/glusterfs/2.0.2/xlator/features/locks.so: undefined symbol: notify -- neglecting<br>
[2009-07-01 18:36:25] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /usr/lib64/glusterfs/2.0.2/xlator/performance/io-threads.so: undefined symbol: notify -- neglecting<br>[2009-07-01 18:36:25] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /usr/lib64/glusterfs/2.0.2/xlator/performance/write-behind.so: undefined symbol: notify -- neglecting<br>
[2009-07-01 18:36:25] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /usr/lib64/glusterfs/2.0.2/xlator/performance/io-cache.so: undefined symbol: notify -- neglecting<br>[2009-07-01 18:36:25] D [glusterfsd.c:1179:main] glusterfs: running in pid 6874<br>
[2009-07-01 18:36:25] D [client-protocol.c:5948:init] compute-5-0: defaulting frame-timeout to 30mins<br>[2009-07-01 18:36:25] D [client-protocol.c:5959:init] compute-5-0: defaulting ping-timeout to 10<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>[2009-07-01 18:36:25] D [client-protocol.c:5948:init] compute-5-1: defaulting frame-timeout to 30mins<br>
[2009-07-01 18:36:25] D [client-protocol.c:5959:init] compute-5-1: defaulting ping-timeout to 10<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>[2009-07-01 18:36:25] D [client-protocol.c:5948:init] compute-5-2: defaulting frame-timeout to 30mins<br>
[2009-07-01 18:36:25] D [client-protocol.c:5959:init] compute-5-2: defaulting ping-timeout to 10<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>[2009-07-01 18:36:25] D [client-protocol.c:5948:init] compute-5-3: defaulting frame-timeout to 30mins<br>
[2009-07-01 18:36:25] D [client-protocol.c:5959:init] compute-5-3: defaulting ping-timeout to 10<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>[2009-07-01 18:36:25] D [unify.c:4288:init] unified: namespace node specified as compute-5-4<br>
[2009-07-01 18:36:25] D [scheduler.c:48:get_scheduler] scheduler: attempt to load file rr.so<br>[2009-07-01 18:36:25] D [unify.c:4320:init] unified: Child node count is 2<br>[2009-07-01 18:36:25] D [rr-options.c:188:rr_options_validate] rr: using scheduler.limits.min-free-disk = 15 [default]<br>
[2009-07-01 18:36:25] D [rr-options.c:216:rr_options_validate] rr: using scheduler.refresh-interval = 10 [default]<br>[2009-07-01 18:36:25] D [client-protocol.c:5948:init] compute-5-4: defaulting frame-timeout to 30mins<br>
[2009-07-01 18:36:25] D [client-protocol.c:5959:init] compute-5-4: defaulting ping-timeout to 10<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-4: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-4: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-4: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-4: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [write-behind.c:1859:init] writebehind: disabling write-behind for first 1 bytes<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-0: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-0: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-1: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-1: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-2: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-2: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-3: got GF_EVENT_PARENT_UP, attempting connect on transport<br>[2009-07-01 18:36:25] D [client-protocol.c:6276:notify] compute-5-3: got GF_EVENT_PARENT_UP, attempting connect on transport<br>
[2009-07-01 18:36:25] D [io-threads.c:2280:init] brick: io-threads: Autoscaling: off, min_threads: 16, max_threads: 16<br>[2009-07-01 18:36:25] D [transport.c:141:transport_load] transport: attempt to load file /usr/lib64/glusterfs/2.0.2/transport/socket.so<br>
[2009-07-01 18:36:25] E [socket.c:206:__socket_server_bind] server: binding to failed: Address already in use<br>[2009-07-01 18:36:25] E [socket.c:209:__socket_server_bind] server: Port is already in use<br>[2009-07-01 18:36:25] E [server-protocol.c:7631:init] server: failed to bind/listen on socket<br>
[2009-07-01 18:36:25] E [xlator.c:736:xlator_init_rec] xlator: Initialization of volume 'server' failed, review your volfile again<br>[2009-07-01 18:36:25] E [glusterfsd.c:498:_xlator_graph_init] glusterfs: initializing translator failed<br>
[2009-07-01 18:36:25] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed. exiting<br>[root@compute-5-0 gluster]# ps aux | grep gluster<br><br></div><div>I think my volfile is wrong, though don't know where is the problem.</div>
<div>BR,</div><div>Gnep</div><div><div class="h5"><br><div class="gmail_quote">On Wed, Jul 1, 2009 at 2:41 PM, Shehjar Tikoo <span dir="ltr"><<a href="mailto:shehjart@gluster.com" target="_blank">shehjart@gluster.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Peng Zhao wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, all,<br>
I'm new to gluster, but found it interesting. I want to setup gluster in a way to be similar with HDFS.<br>
There is my sample vol-file:<br>
volume posix<br>
type storage/posix<br>
option directory /data1/gluster<br>
end-volume<br>
<br>
volume locks<br>
type features/locks<br>
subvolumes posix<br>
end-volume<br>
<br>
volume brick<br>
type performance/io-threads<br>
subvolumes locks<br>
end-volume<br>
<br>
volume server<br>
type protocol/server<br>
option transport-type tcp<br>
option auth.addr.brick.allow *<br>
subvolumes brick<br>
end-volume<br>
<br>
volume compute-5-0<br>
type protocol/client<br>
option transport-type tcp<br>
option remote-host compute-5-0<br>
option remote-subvolume brick<br>
end-volume<br>
<br>
volume compute-5-1<br>
type protocol/client<br>
option transport-type tcp<br>
option remote-host compute-5-1<br>
option remote-subvolume brick<br>
end-volume<br>
<br>
volume compute-5-2<br>
type protocol/client<br>
option transport-type tcp<br>
option remote-host compute-5-2<br>
option remote-subvolume brick<br>
end-volume<br>
<br>
volume compute-5-3<br>
type protocol/client<br>
option transport-type tcp<br>
option remote-host compute-5-3<br>
option remote-subvolume brick<br>
end-volume<br>
<br>
volume compute-5-4<br>
type protocol/client<br>
option transport-type tcp<br>
option remote-host compute-5-4<br>
option remote-subvolume brick-ns<br>
end-volume<br>
<br>
volume primary<br>
type cluster/replicate<br>
option local-volume-name primary<br>
subvolumes compute-5-0 compute-5-1<br>
end-volume<br>
<br>
volume secondary<br>
type cluster/replicate<br>
option local-volume-name secondary<br>
subvolumes compute-5-2 compute-5-3<br>
end-volume<br>
<br>
volume unified<br>
type cluster/unify<br>
option scheduler rr<br>
option local-volume-name unified # do I need this?<br>
option namespace compute-5-4 # do I need this?<br>
subvolumes primary secondary<br>
end-volume<br>
<br>
volume writebehind<br>
type performance/write-behind<br>
option cache-size 1MB<br>
subvolumes unified<br>
end-volume<br>
<br>
volume cache<br>
type performance/io-cache<br>
option cache-size 512MB<br>
subvolumes writebehind<br>
end-volume<br>
<br>
The glusterd is up & running and no error msg in the logs. However, it reports some error when I tried to mount it:<br>
[2009-07-01 09:37:36] E [xlator.c:736:xlator_init_rec] xlator: Initialization of volume 'fuse' failed, review your volfile again<br>
[2009-07-01 09:37:36] E [glusterfsd.c:498:_xlator_graph_init] glusterfs: initializing translator failed<br>
[2009-07-01 09:37:36] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed. exiting<br>
<br>
I guess it is a very common question. Anyone has any idea?<br>
BR,<br>
</blockquote>
<br></div></div>
Try generating the log file with log-level set to bug. You<br>
can do so by using the "-L DEBUG" command line parameter.<br>
<br>
The debug log level will give us a better idea of what<br>
exactly is failing.<br>
<br>
-Shehjar<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Gnep<br>
<br>
<br>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
</blockquote>
<br>
</blockquote></div><br>
</div></div></blockquote></div><br>