I had this morning a similar situation. Here is my log.<br>Till this morning (30/4) it was working fine . I'm running now 2.0.0rc8<br><br>2009-04-21 22:22:31 N [glusterfsd.c:1152:main] glusterfs: Successfully started<br>
2009-04-21 22:22:31 N [client-protocol.c:6327:client_setvolume_cbk] brick1: connection and handshake succeeded<br>2009-04-21 22:22:31 N [afr.c:2126:notify] afr: subvolume brick1 came up<br>2009-04-21 22:22:31 N [client-protocol.c:6327:client_setvolume_cbk] brick1: connection and handshake succeeded<br>
2009-04-21 22:22:31 N [afr.c:2126:notify] afr: subvolume brick1 came up<br>2009-04-21 22:22:31 N [client-protocol.c:6327:client_setvolume_cbk] brick2: connection and handshake succeeded<br>2009-04-21 22:22:31 N [afr.c:2126:notify] afr: subvolume brick2 came up<br>
2009-04-21 22:22:31 N [client-protocol.c:6327:client_setvolume_cbk] brick2: connection and handshake succeeded<br>2009-04-21 22:22:31 N [afr.c:2126:notify] afr: subvolume brick2 came up<br>2009-04-22 06:35:07 W [afr-self-heal-common.c:1161:sh_missing_entries_lookup_cbk] afr: path /wordpress/wp-content/uploads/js_cache/tinymce_a12248cba65d26d1835b9b337723f188.gz on subvolume brick2 => -1 (No such file or directory)<br>
2009-04-22 06:35:07 W [afr-self-heal-data.c:646:afr_sh_data_open_cbk] afr: sourcing file /wordpress/wp-content/uploads/js_cache/tinymce_a12248cba65d26d1835b9b337723f188.gz from brick1 to other sinks<br>pending frames:<br>
frame : type(1) op(READ)<br><br>patchset: 82394d484803e02e28441bc0b988efaaff60dd94<br>signal received: 11<br>configuration details:argp 1<br>backtrace 1<br>bdb->cursor->get 1<br>db.h 1<br>dlfcn 1<br>fdatasync 1<br>libpthread 1<br>
llistxattr 1<br>setfsid 1<br>spinlock 1<br>epoll.h 1<br>xattr.h 1<br>st_atim.tv_nsec 1<br>package-string: glusterfs 2.0.0rc8<br>/lib/libc.so.6[0x7fbb7ffb3100]<br>/usr/local/lib/glusterfs/2.0.0rc8/xlator/protocol/client.so(client_readv_cbk+0x15d)[0x7fbb7f5788cd]<br>
/usr/local/lib/glusterfs/2.0.0rc8/xlator/protocol/client.so(protocol_client_pollin+0xca)[0x7fbb7f5670ca]<br>/usr/local/lib/glusterfs/2.0.0rc8/xlator/protocol/client.so(notify+0x10b)[0x7fbb7f56e75b]<br>/usr/local/lib/glusterfs/2.0.0rc8/transport/socket.so(socket_event_handler+0xcb)[0x7fbb7eaf1aeb]<br>
/usr/local/lib/libglusterfs.so.0[0x7fbb8072abea]<br>/usr/local/sbin/glusterfs(main+0xa38)[0x403aa8]<br>/lib/libc.so.6(__libc_start_main+0xf4)[0x7fbb7ff9f1c4]<br>/usr/local/sbin/glusterfs[0x4026c9]<br>---------<br>================================================================================<br>
<br>Client configuration is very simple:<br><br>volume brick2<br> type protocol/client<br> option transport-type tcp/client # for TCP/IP transport<br> option remote-host 192.168.100.39 # IP address of server2<br>
option remote-subvolume brick # name of the remote volume on server2<br>end-volume<br><br>volume brick1<br> type protocol/client<br> option transport-type tcp/client # for TCP/IP transport<br> option remote-host 192.168.100.38 # IP address of server1<br>
option remote-subvolume brick # name of the remote volume on server1<br>end-volume<br><br>volume afr<br> type cluster/afr<br> option metadata-self-heal on<br> subvolumes brick1 brick2<br>end-volume<br><br>Enrico<br>
<br><br><br><div class="gmail_quote">2009/4/26 JV <span dir="ltr"><<a href="mailto:jamson@megatek.lv">jamson@megatek.lv</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello.<br>
<br>
There wasn't anything interesting:<br>
<br>
================================================================================<br>
Version : glusterfs 2.0.0rc8 built on Apr 20 2009 23:04:47<br>
TLA Revision : 82394d484803e02e28441bc0b988efaaff60dd94<br>
Starting Time: 2009-04-23 17:17:31<br>
Command line : /usr/local/sbin/glusterfs --log-level=NORMAL --volfile=/etc/glusterfs/glusterfs-client.vol /<br>
mnt/glusterfs<br>
PID : 3759<br>
System name : Linux<br>
Nodename : f1<br>
Kernel Release : 2.6.29.1<br>
Hardware Identifier: i686<br>
<br>
Given volfile:<br>
+------------------------------------------------------------------------------+<br>
1: volume g1b1<br>
2: type protocol/client<br>
3: option transport-type tcp/client<br>
4: option remote-host 10.10.70.2<br>
5: option remote-subvolume brick1<br>
6: end-volume<br>
7: volume g1b2<br>
8: type protocol/client<br>
9: option transport-type tcp<br>
10: option remote-host 10.10.70.2<br>
11: option remote-subvolume brick2<br>
12: end-volume<br>
13: volume g1b3<br>
14: type protocol/client<br>
15: option transport-type tcp<br>
16: option remote-host 10.10.70.2<br>
17: option remote-subvolume brick3<br>
18: end-volume<br>
19:<br>
20: volume g2b1<br>
21: type protocol/client<br>
22: option transport-type tcp/client<br>
23: option remote-host 10.10.70.3<br>
24: option remote-subvolume brick1<br>
25: end-volume<br>
26: volume g2b2<br>
27: type protocol/client<br>
28: option transport-type tcp<br>
29: option remote-host 10.10.70.3<br>
30: option remote-subvolume brick2<br>
31: end-volume<br>
32: volume g2b3<br>
33: type protocol/client<br>
34: option transport-type tcp<br>
35: option remote-host 10.10.70.3<br>
36: option remote-subvolume brick3<br>
37: end-volume<br>
38:<br>
39: volume replicate1<br>
40: type cluster/replicate<br>
41: subvolumes g1b1 g2b1<br>
42: end-volume<br>
43:<br>
44: volume replicate2<br>
45: type cluster/replicate<br>
46: subvolumes g1b2 g2b2<br>
47: end-volume<br>
48:<br>
49: volume replicate3<br>
50: type cluster/replicate<br>
51: subvolumes g1b3 g2b3<br>
52: end-volume<br>
53:<br>
54: volume distribute<br>
55: type cluster/distribute<br>
56: subvolumes replicate1 replicate2 replicate3<br>
57: end-volume<br>
58:<br>
<br>
+------------------------------------------------------------------------------+<br>
2009-04-23 17:17:31 N [glusterfsd.c:1152:main] glusterfs: Successfully started<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b1: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate1: subvolume g1b1 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b1: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate1: subvolume g1b1 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b1: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate1: subvolume g2b1 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b2: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate2: subvolume g1b2 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b1: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate1: subvolume g2b1 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b2: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate2: subvolume g1b2 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b2: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate2: subvolume g2b2 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b2: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate2: subvolume g2b2 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b3: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate3: subvolume g1b3 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b3: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate3: subvolume g2b3 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g1b3: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate3: subvolume g1b3 came up<br>
2009-04-23 17:17:31 N [client-protocol.c:6327:client_setvolume_cbk] g2b3: connection and handshake succeeded<br>
2009-04-23 17:17:31 N [afr.c:2126:notify] replicate3: subvolume g2b3 came up<div class="im"><br>
pending frames:<br>
<br>
patchset: 82394d484803e02e28441bc0b988efaaff60dd94<br>
signal received: 6<br>
configuration details:argp 1<br>
backtrace 1<br>
dlfcn 1<br>
fdatasync 1<br>
libpthread 1<br>
llistxattr 1<br>
setfsid 1<br>
spinlock 1<br>
epoll.h 1<br>
xattr.h 1<br>
st_atim.tv_nsec 1<br>
package-string: glusterfs 2.0.0rc8<br></div>
[0xb803c400]<br>
/lib/i686/cmov/libc.so.6(abort+0x188)[0xb7eb3018]<br>
/lib/i686/cmov/libc.so.6(__assert_fail+0xee)[0xb7eaa5be]<br>
/lib/i686/cmov/libpthread.so.0(pthread_mutex_lock+0x5d4)[0xb7fe8f54]<br>
/usr/lib/libfuse.so.2[0xb75c0425]<br>
/usr/local/lib/glusterfs/2.0.0rc8/xlator/mount/fuse.so[0xb75d519a]<br>
/usr/lib/libfuse.so.2[0xb75c1cf8]<br>
/usr/lib/libfuse.so.2[0xb75c2211]<br>
/usr/lib/libfuse.so.2(fuse_session_process+0x26)[0xb75c3bf6]<br>
/usr/local/lib/glusterfs/2.0.0rc8/xlator/mount/fuse.so[0xb75d5f31]<br>
/lib/i686/cmov/libpthread.so.0[0xb7fe74c0]<br>
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb7f666de]<br>
---------<br>
<br>
<br>
Anyhow - it seems to be working without problems using<br>
git version 689347f278e5acfda95a24f7804a1450043311f3<br>
<br>
Also it seems to be working faster without any performance translators, however gluster is using only part of dedicated GigE link - no more than 25% for writing and 30% for reading on client. Half that on each storage node. What can I do to improve this?<br>
<br>
P.S. sorry for the late response - your message got into junk folder.<br>
<br>
JV<div><div></div><div class="h5"><br>
<br>
Anand Avati wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There has to be some more before this. Can you paste the full log?<br>
<br>
Avati<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
in client log is only this:<br>
<br>
pending frames:<br>
<br>
patchset: 82394d484803e02e28441bc0b988efaaff60dd94<br>
signal received: 6<br>
configuration details:argp 1<br>
backtrace 1<br>
dlfcn 1<br>
fdatasync 1<br>
libpthread 1<br>
llistxattr 1<br>
setfsid 1<br>
spinlock 1<br>
epoll.h 1<br>
xattr.h 1<br>
st_atim.tv_nsec 1<br>
package-string: glusterfs 2.0.0rc8<br>
[0xb8067400]<br>
/lib/i686/cmov/libc.so.6(abort+0x188)[0xb7ede018]<br>
/lib/i686/cmov/libc.so.6(__assert_fail+0xee)[0xb7ed55be]<br>
/lib/i686/cmov/libpthread.so.0(pthread_mutex_lock+0x5d4)[0xb8013f54]<br>
/usr/lib/libfuse.so.2[0xb75d3147]<br>
/usr/lib/libfuse.so.2(fuse_session_process+0x26)[0xb75d4bf6]<br>
/usr/local/lib/glusterfs/2.0.0rc8/xlator/mount/fuse.so[0xb75eef31]<br>
/lib/i686/cmov/libpthread.so.0[0xb80124c0]<br>
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb7f916de]<br>
---------<br>
</blockquote></blockquote>
<br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-------------<br>Enrico Zaffaroni<br><a href="mailto:ezaffa@gmail.com">ezaffa@gmail.com</a><br>