Today my glusterFS system, which had been stable for about 4 months or so (1.3.10) started crashing on me for no discernible reason. I can start the system up all right, but as soon as I try to access some of my directories the whole system will freeze and then generally the backend goes down (I get transport not connected). This takes several minutes - logfiles attached, as well as config files. Can anyone suggest why this might have suddenly started happening? - Will Server config: ### file: glusterfs-server.vol # Local volumes exported by the server volume brick0 type storage/posix # POSIX FS translator option directory /mnt/brick0 # Export this directory end-volume volume brick0-locks type features/posix-locks subvolumes brick0 option mandatory on end-volume volume brick1 type storage/posix # POSIX FS translator option directory /mnt/brick1 # Export this directory end-volume volume brick1-locks type features/posix-locks subvolumes brick1 option mandatory on end-volume volume brick2 type storage/posix # POSIX FS translator option directory /mnt/brick2 # Export this directory end-volume volume brick2-locks type features/posix-locks subvolumes brick2 option mandatory on end-volume volume brick3 type storage/posix # POSIX FS translator option directory /mnt/brick3 # Export this directory end-volume volume brick3-locks type features/posix-locks subvolumes brick3 option mandatory on end-volume volume brick4 type storage/posix # POSIX FS translator option directory /mnt/brick4 # Export this directory end-volume volume brick4-locks type features/posix-locks subvolumes brick4 option mandatory on end-volume volume brick5 type storage/posix # POSIX FS translator option directory /mnt/brick5 # Export this directory end-volume volume brick5-locks type features/posix-locks subvolumes brick5 option mandatory on end-volume volume brick6 type storage/posix # POSIX FS translator option directory /mnt/brick6 # Export this directory end-volume volume brick6-locks type features/posix-locks subvolumes brick6 option mandatory on end-volume volume brick7 type storage/posix # POSIX FS translator option directory /mnt/brick7 # Export this directory end-volume volume brick7-locks type features/posix-locks subvolumes brick7 option mandatory on end-volume volume brick-ns type storage/posix # POSIX FS translator option directory /mnt/brick-ns # Export this directory end-volume volume brick-ns-locks type features/posix-locks subvolumes brick-ns option mandatory on end-volume # Configure the glusterfs server side features volume server type protocol/server option transport-type tcp/server option client-volume-filename /usr/etc/glusterfs/glusterfs-client.vol subvolumes brick0-locks brick1-locks brick2-locks brick3-locks brick4-locks brick5-locks brick6-locks brick7-locks brick-ns-locks option auth.ip.brick0-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick1-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick2-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick3-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick4-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick5-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick6-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick7-locks.allow 127.0.0.1,192.168.1.1 option auth.ip.brick-ns-locks.allow 127.0.0.1,192.168.1.1 end-volume Client config: ### file: glusterfs-client.vol volume brick0 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick0-locks end-volume volume brick1 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick1-locks end-volume volume brick2 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick2-locks end-volume volume brick3 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick3-locks end-volume volume brick4 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick4-locks end-volume volume brick5 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick5-locks end-volume volume brick6 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick6-locks end-volume volume brick7 type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick7-locks end-volume volume brick-ns type protocol/client option transport-type tcp/client option remote-host 127.0.0.1 option remote-subvolume brick-ns-locks end-volume volume unify type cluster/unify subvolumes brick0 brick1 brick2 brick3 brick4 brick5 brick6 brick7 option namespace brick-ns option scheduler rr option rr.limits.min-free-disk 5% # Unit in % option rr.refresh-interval 10 # Check server brick after 10s. end-volume Log from an event: 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick-ns: activating bail-out. pending frames = 11. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick-ns: bailing transport 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick-ns: cleaning up state in transport object 0x521cd0 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick0: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(36) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4208:client_setdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(23) reply=@0x524450 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick0: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:3303:client_getdents_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick1: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick1: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick2: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick2: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick1: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick3: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick3: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick2: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick4: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick4: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick3: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick5: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick5: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick4: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick6: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick6: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick5: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:205:call_bail] brick7: activating bail-out. pending frames = 2. last sent = 2008-09-15 03:26:44. last received = 2008-09-15 03:26:21 transport-timeout = 42 2008-09-15 03:27:33 C [client-protocol.c:212:call_bail] brick7: bailing transport 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick6: transport_submit failed 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick7: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:1711:client_closedir] brick-ns: no proper fd found, returning 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x524450 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick7: cleaning up state in transport object 0x51eb40 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x527ad0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x527ad0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(24) reply=@0x527ad0 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick6: cleaning up state in transport object 0x51c6c0 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x526d80 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x526d80 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(24) reply=@0x526d80 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick5: cleaning up state in transport object 0x51a240 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x525fc0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x525fc0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(24) reply=@0x525fc0 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick4: cleaning up state in transport object 0x517dc0 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(24) reply=@0x5250c0 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick3: cleaning up state in transport object 0x515940 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x524f30 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x524f30 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(24) reply=@0x524f30 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick2: cleaning up state in transport object 0x5134c0 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x524da0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x524da0 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(24) reply=@0x524da0 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick1: cleaning up state in transport object 0x511040 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x524c10 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x524c10 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(24) reply=@0x524c10 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 W [client-protocol.c:4777:client_protocol_cleanup] brick0: cleaning up state in transport object 0x50e720 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x524a90 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:27:33 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 118: (34) / => -1 (107) 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x524a90 2008-09-15 03:27:33 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:27:33 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 119: (34) / => -1 (107) 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(24) reply=@0x524a90 2008-09-15 03:27:33 E [client-protocol.c:3820:client_closedir_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:33 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:27:35 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:17 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:28:36 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(15) with handshake 2008-09-15 03:29:03 W [client-protocol.c:205:call_bail] brick-ns: activating bail-out. pending frames = 6. last sent = 2008-09-15 03:28:17. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:03 C [client-protocol.c:212:call_bail] brick-ns: bailing transport 2008-09-15 03:29:03 W [client-protocol.c:4777:client_protocol_cleanup] brick-ns: cleaning up state in transport object 0x521cd0 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:03 E [client-protocol.c:4827:client_protocol_cleanup] brick-ns: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:03 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:03 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick1: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick1: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick1: cleaning up state in transport object 0x511040 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick2: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick2: bailing transport 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(15) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick1 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick3: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick3: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick2: cleaning up state in transport object 0x5134c0 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(15) reply=@0x517e50 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick2 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick4: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick4: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick3: cleaning up state in transport object 0x515940 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(15) reply=@0x5110d0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick3 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick5: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick5: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick4: cleaning up state in transport object 0x517dc0 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(15) reply=@0x50e7b0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick4 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick6: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick6: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick5: cleaning up state in transport object 0x51a240 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(15) reply=@0x5250c0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick5 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick7: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick7: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick6: cleaning up state in transport object 0x51c6c0 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(15) reply=@0x5253e0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick6 (107) 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick7: cleaning up state in transport object 0x51eb40 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(15) reply=@0x51a2d0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick7 (107) 2008-09-15 03:29:24 W [client-protocol.c:205:call_bail] brick0: activating bail-out. pending frames = 7. last sent = 2008-09-15 03:28:36. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:29:24 C [client-protocol.c:212:call_bail] brick0: bailing transport 2008-09-15 03:29:24 W [client-protocol.c:4777:client_protocol_cleanup] brick0: cleaning up state in transport object 0x50e720 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 118: (34) / => -1 (2) 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 119: (34) / => -1 (2) 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:24 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 121: (34) /home => -1 (107) 2008-09-15 03:29:24 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:29:24 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:24 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:29:24 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:24 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:29:24 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:24 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 122: (34) / => -1 (107) 2008-09-15 03:29:24 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:29:24 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(34) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:24 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 123: (34) / => -1 (107) 2008-09-15 03:29:24 W [client-protocol.c:280:client_protocol_xfer] brick0: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:29:24 E [client-protocol.c:325:client_protocol_xfer] brick0: transport_submit failed 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:24 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [client-protocol.c:4827:client_protocol_cleanup] brick0: forced unwinding frame type(1) op(15) reply=@0x528cd0 2008-09-15 03:29:24 E [client-protocol.c:3884:client_statfs_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:24 E [unify.c:1401:unify_statfs_cbk] unify: operation failed on brick0 (107) 2008-09-15 03:29:24 E [fuse-bridge.c:2064:fuse_statfs_cbk] glusterfs-fuse: 124: ERR => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 127: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 127: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 128: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 128: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 129: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 130: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 130: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 131: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 131: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 132: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 133: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 133: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 134: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 134: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 135: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 136: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 136: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 137: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 137: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 138: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 139: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 139: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 140: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 140: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 141: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 142: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 142: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 143: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 143: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 144: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 145: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 145: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 146: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 146: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 147: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 148: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 148: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 149: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 149: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 150: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 151: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 151: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 152: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 152: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 153: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 154: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 154: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 155: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 155: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 156: (0) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 157: (34) / => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 157: (34) / => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 158: (34) /downloads => -1 (107) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick1: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick2: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick3: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick4: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick5: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick6: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick7: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:29:25 E [client-protocol.c:4423:client_lookup_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [fuse-bridge.c:468:fuse_entry_cbk] glusterfs-fuse: 158: (34) /downloads => -1 (2) 2008-09-15 03:29:25 W [client-protocol.c:332:client_protocol_xfer] brick-ns: not connected at the moment to submit frame type(1) op(0) 2008-09-15 03:29:25 E [client-protocol.c:2681:client_stat_cbk] brick-ns: no proper reply from server, returning ENOTCONN 2008-09-15 03:29:25 E [unify.c:118:unify_buf_cbk] unify: brick-ns returned 107 2008-09-15 03:29:25 E [fuse-bridge.c:589:fuse_attr_cbk] glusterfs-fuse: 159: (0) /downloads => -1 (107) 2008-09-15 03:30:01 W [client-protocol.c:332:client_protocol_xfer] brick0: not connected at the moment to submit frame type(1) op(34) 2008-09-15 03:30:01 E [client-protocol.c:4423:client_lookup_cbk] brick0: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:01 E [unify.c:182:unify_lookup_cbk] unify: brick0 returned 107 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick1: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick2: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick3: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick4: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick5: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick6: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick7: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:01 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(34) with handshake 2008-09-15 03:30:35 W [client-protocol.c:280:client_protocol_xfer] brick-ns: attempting to pipeline request type(1) op(0) with handshake 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick7: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick7: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick7: cleaning up state in transport object 0x51eb40 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick6: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick6: bailing transport 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick7: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick7: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick7 returned 107 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick5: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick5: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick6: cleaning up state in transport object 0x51c6c0 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick6: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick6: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick6 returned 107 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick4: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick4: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick5: cleaning up state in transport object 0x51a240 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick5: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick5: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick5 returned 107 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick3: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick3: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick4: cleaning up state in transport object 0x517dc0 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick4: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick4: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick4 returned 107 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick2: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick2: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick3: cleaning up state in transport object 0x515940 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick3: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick3: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick3 returned 107 2008-09-15 03:30:45 W [client-protocol.c:205:call_bail] brick1: activating bail-out. pending frames = 1. last sent = 2008-09-15 03:30:01. last received = 1970-01-01 10:00:00 transport-timeout = 42 2008-09-15 03:30:45 C [client-protocol.c:212:call_bail] brick1: bailing transport 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick2: cleaning up state in transport object 0x5134c0 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick2: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick2: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick2 returned 107 2008-09-15 03:30:45 W [client-protocol.c:4777:client_protocol_cleanup] brick1: cleaning up state in transport object 0x511040 2008-09-15 03:30:45 E [client-protocol.c:4827:client_protocol_cleanup] brick1: forced unwinding frame type(1) op(34) reply=@0x521d60 2008-09-15 03:30:45 E [client-protocol.c:4423:client_lookup_cbk] brick1: no proper reply from server, returning ENOTCONN 2008-09-15 03:30:45 E [unify.c:182:unify_lookup_cbk] unify: brick1 returned 107 2008-09-15 03:30:45 E [fuse-bridge.c:2549:fuse_thread_proc] glusterfs-fuse: fuse_chan_receive() returned -1 (25) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20080915/80358644/attachment-0001.htm