Stephan von Krawczynski wrote:
Hello all,
I am evaluating glusterfs currently and therefore use a testbed consisting of
four (real) boxes, two configured as fileservers, two as clients, see configs
below.
All I have to do to make the fs hang on both clients (sooner or later) is to
run bonnie (a simple fs check program) constantly on the mounted tree.
I'm seeing similar problems with 2.0.1 -- any log entries? I get a lot
of these in glusterfs.log when mine hangs:
[2009-06-11 05:10:51] E [client-protocol.c:292:call_bail] zircon:
bailing out frame STATFS(15) frame sent = 2009-06-11 04:40:50.
frame-timeout = 1800
[2009-06-11 05:10:52] W
[client-protocol.c:5869:protocol_client_interpret] zircon: no frame for
callid=1913585 type=4 op=29
[2009-06-11 05:10:52] W
[client-protocol.c:5869:protocol_client_interpret] zircon: no frame for
callid=2706745 type=4 op=40
My setup is very close to yours -- using replicate, iocache, readahead,
and writebehind on the client and iothreads on the servers. The thread
below sounds like my problem, but I don't have autoscaling (explicitly)
turned on:
http://www.mail-archive.com/gluster-de...@nongnu.org/msg06140.html
...so I'm wondering if it could be something else.
-Matt
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
