Re: [Gluster-users] GlusterFS 3.1.1 - peer attach bug
Kon, I will try to reproduce this locally and file a bug. -Jacob -Original Message- From: Kon Wilms [mailto:kon...@gmail.com] Sent: Thursday, December 09, 2010 2:47 PM To: Jacob Shucart Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] GlusterFS 3.1.1 - peer attach bug On Thu, Dec 9, 2010 at 2:08 PM, Jacob Shucart ja...@gluster.com wrote: Can you tell me a little more about the node? Does it have several IP addresses? Did you get the same results with all of the IP addresses? Or just one of them? When I tried to probe the IP address of the local node, I received a message: Probe on localhost not needed This is the expected behavior. One on the backend with a pair of bonded interfaces, one on the frontend for gfs access, and another on the frontend (virtual) for ucarp: bond0 Link encap:Ethernet HWaddr a4:ba:db:0c:59:4f inet addr:172.16.16.50 Bcast:172.16.16.0 Mask:255.255.255.0 eth0 Link encap:Ethernet HWaddr a4:ba:db:0c:59:4b inet addr:10.2.16.50 Bcast:10.2.31.255 Mask:255.255.240.0 eth2 Link encap:Ethernet HWaddr a4:ba:db:0c:59:4f UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1 eth3 Link encap:Ethernet HWaddr a4:ba:db:0c:59:4f UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 eth0:ucarp Link encap:Ethernet HWaddr a4:ba:db:0c:59:4b inet addr:10.2.16.57 Bcast:10.2.31.255 Mask:255.255.240.0 I get the probe not needed response as you do, but a peer status displays the bogus local node with nulled uuid (which cannot be deleted except for doing it manually). Cheers Kon ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] GlusterFS 3.1.1 - peer attach bug
Not sure where to file this so I am posting it here. Attaching the local brick's ip address results in a disconnect and the peer cannot be removed. - server x.x.x.x gluster peer probe x.x.x.x - Issuing a gluster peer status shows x.x.x.x as disconnected with uuid of zeros. This is replicated to other bricks. - gluster peer detach x.x.x.x has no effect. The only resolution is to stop the gluster service on all nodes and remove the offending node from /etc/glusterd/peers on all nodes, and restart glusterd on all nodes. Gluster should prevent this from happening in the first place. Cheers Kon ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] GlusterFS 3.1.1 - peer attach bug
Kon, Can you tell me a little more about the node? Does it have several IP addresses? Did you get the same results with all of the IP addresses? Or just one of them? When I tried to probe the IP address of the local node, I received a message: Probe on localhost not needed This is the expected behavior. -Jacob -Original Message- From: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] On Behalf Of Kon Wilms Sent: Thursday, December 09, 2010 10:30 AM To: gluster-users@gluster.org Subject: [Gluster-users] GlusterFS 3.1.1 - peer attach bug Not sure where to file this so I am posting it here. Attaching the local brick's ip address results in a disconnect and the peer cannot be removed. - server x.x.x.x gluster peer probe x.x.x.x - Issuing a gluster peer status shows x.x.x.x as disconnected with uuid of zeros. This is replicated to other bricks. - gluster peer detach x.x.x.x has no effect. The only resolution is to stop the gluster service on all nodes and remove the offending node from /etc/glusterd/peers on all nodes, and restart glusterd on all nodes. Gluster should prevent this from happening in the first place. Cheers Kon ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
