the bound_xl error is most likely because your client and servers are from differnt versions. do you have logs from the time when you get the vi warning? avati 2008/5/22 Rohan <rohan.thale@xxxxxxxxxxxxxxxx>: > Hi Avati, > > > > We've been testing Glusterfs 1.3.9 for few days. Most of the errors are not > cropping up now. > > > > > > I got following error. I couldn't understand what dose this mean. > > > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.11.25:1013) > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.51:1018) > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.51:1017) > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.51:1016) > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.51:1015) > > 2008-05-22 09:32:19 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.30.51:1014) > > 2008-05-22 09:32:22 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:22 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:23 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:24 E [server-protocol.c:6040:server_protocol_interpret] > server: bound_xl is null > > 2008-05-22 09:32:26 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.11.23:1015) > > 2008-05-22 09:32:27 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.11.23:1013) > > 2008-05-22 09:32:27 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.11.23:1012) > > 2008-05-22 09:32:27 E [protocol.c:271:gf_block_unserialize_transport] > server: EOF from peer (172.30.11.23:1010) > > > > Also I'm facing one weird problem. If I open any file for editing in vi, > after some time when I try to save it I get following error. > > > > "test.sh" > > WARNING: The file has been changed since reading it!!! > > Do you really want to write to it (y/n)? > > > > 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.
