Rohan, these client errors are mostly due to presence of 0 byte files in the backend storage, which was present in patch-636 to patch-641. If you don't have any important data in the backend. Can you start fresh with the latest source? That should solve it. Regards, -Amar On Jan 31, 2008 3:30 PM, Rohan <rohan.thale@xxxxxxxxxxxxxxxx> wrote: > Hi Guys, > > > > Please help with, we want to put this in production. > > > > FYI: Before this TLA 643 version and without self-heal off, 0Kb files got > created on servers. > > > > > > I'm running glusterfs on physical machine. Currently I'm testing TLA 643 > with "self-heal off". And I'm getting following error > > > > Client config: http://glusterfs.pastebin.com/m7d6d3c3 > > > > Server config: http://glusterfs.pastebin.com/m619775e4 > > > > > > > > > > Client1 error. > > > > 2008-01-31 14:34:24 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 135: /IOtest/ACT-SM-002-R10.C1.DB.dc1.in.com => -1 (2) > > 2008-01-31 14:34:24 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 135: /IOtest/ACT-SM-002-R10.C1.DB.dc1.in.com => -1 (2) > > 2008-01-31 15:09:17 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201785: / => -1 (116) > > 2008-01-31 15:09:17 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201786: / => -1 (116) > > 2008-01-31 15:09:17 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201788: / => -1 (116) > > 2008-01-31 15:09:18 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201792: / => -1 (116) > > 2008-01-31 15:09:18 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201793: / => -1 (116) > > 2008-01-31 15:09:18 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201795: / => -1 (116) > > 2008-01-31 15:09:19 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201800: / => -1 (116) > > 2008-01-31 15:09:20 E [fuse-bridge.c:431:fuse_entry_cbk] glusterfs-fuse: > 201806: / => -1 (116) > > > > Client2 error: http://glusterfs.pastebin.com/m566518a7 > > > > Server error > > > > 2008-01-31 14:06:16 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:1019) > > 2008-01-31 14:06:16 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:16 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:1020) > > 2008-01-31 14:06:16 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:16 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:1021) > > 2008-01-31 14:06:16 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:16 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:1022) > > 2008-01-31 14:06:16 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:16 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:1023) > > 2008-01-31 14:06:16 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:37 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:972) > > 2008-01-31 14:06:37 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:37 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:975) > > 2008-01-31 14:06:37 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:37 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:962) > > 2008-01-31 14:06:37 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:37 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:966) > > 2008-01-31 14:06:37 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:06:37 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:969) > > 2008-01-31 14:06:37 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:07:31 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:918) > > 2008-01-31 14:07:31 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:07:31 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:921) > > 2008-01-31 14:07:31 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:07:31 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:924) > > 2008-01-31 14:07:31 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:07:31 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:927) > > 2008-01-31 14:07:31 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:07:31 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:915) > > 2008-01-31 14:07:31 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:43:06 E [server-protocol.c:178:generic_reply] server: > transport_writev failed > > 2008-01-31 14:43:06 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:43:06 E [tcp.c:118:tcp_except] server: shutdown () - error: > Transport endpoint is not connected > > 2008-01-31 14:43:06 E [server-protocol.c:178:generic_reply] server: > transport_writev failed > > 2008-01-31 14:43:06 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:43:06 E [server-protocol.c:178:generic_reply] server: > transport_writev failed > > 2008-01-31 14:43:06 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:43:06 E [server-protocol.c:178:generic_reply] server: > transport_writev failed > > 2008-01-31 14:43:06 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > 2008-01-31 14:43:06 E [server-protocol.c:178:generic_reply] server: > transport_writev failed > > 2008-01-31 14:43:06 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > > > > > > > > ------------------------------ > > *From:* anand.avati@xxxxxxxxx [mailto:anand.avati@xxxxxxxxx] *On Behalf Of > *Anand Avati > *Sent:* Thursday, January 31, 2008 3:04 PM > *To:* Rohan > *Cc:* Gluster-devel@xxxxxxxxxx > *Subject:* Re: error gf_block_unserialize_transport > server: EOF from peer > > > > Rohan, > are you running glusterfs client or server on a virtual machine or a > physical machine? > > avati > > 2008/1/25, Rohan <rohan.thale@xxxxxxxxxxxxxxxx>: > > I'm getting following error. Also sometime ls hangs. > > > > > > 2008-01-25 19:37:19 E [protocol.c:254:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.22:932) > > 2008-01-25 19:37:19 C [tcp.c:81:tcp_disconnect] server: connection > disconnected > > > > > > 1. client > 2. afr > 3. unify > 4. io-threads > 5. write-behind > 6. io-cache > > > > > > Please help > > > > Rohan > > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > > > > > -- > If I traveled to the end of the rainbow > As Dame Fortune did intend, > Murphy would be there to tell me > The pot's at the other end. > -- Amar Tumballi Gluster/GlusterFS Hacker [bulde on #gluster/irc.gnu.org] http://www.zresearch.com - Commoditizing Supercomputing and Superstorage!
