Hi Sean,<br> We haven't yet got a chance to test glusterfs over PPC architecture. It works fine with intel architecture of Mac OS. Looks like protocol interpretation problem.<br><br>Regards,<br>Amar<br><br><div class="gmail_quote">
On Mon, Mar 9, 2009 at 1:34 PM, Sean Davis <span dir="ltr"><<a href="mailto:sdavis2@mail.nih.gov">sdavis2@mail.nih.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have successfully gotten glusterfs (2.0rc4) compiled on a PPC-based xserve running OS 10.5. I have a pretty simple volume file using transport-type tcp. I can successfully run glusterfsd and everything looks OK. Also, using the glusterfs volume on the machine locally works just fine. However, when I try to include the Mac OS server into a distribute container, I get errors like:<br>
<br>2009-03-09 16:19:26 N [server-protocol.c:8048:notify] server: xx.xx.209.230:1014 disconnected<br>2009-03-09 16:19:26 E [socket.c:480:__socket_proto_validate_header] server: socket header has incorrect size1=318832640<br>
2009-03-09 16:19:26 E [socket.c:583:__socket_proto_state_machine] server: socket header validate failed (xx.xx.209.230:1013). possible mismatch of transport-type between server and client volumes, or version mismatch<br>
<br>
Both server and client are using 2.0rc4, downloaded today. The client in the second case is a linux machine (and glusterfs works flawless on it and other linux machines). Any ideas?<br><br>Thanks,<br><font color="#888888">Sean<br>
<br>
</font><br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Amar Tumballi<br><br>