-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Ross S. W. Walker Sent: Thursday, May 31, 2007 2:31 PM To: CentOS mailing list Subject: [CentOS] 4.5 ALB Bonding Hang on Shutdown
Since I upgraded from 4.4 to 4.5 my system which has 2 sets of ALB bonded interfaces hangs on shutdown while doing an ifdown on these interfaces.
Has anyone else seen this issue with 4.5 and bonding?
I think I found the answer. The new version of bonding has a bug in it that doesn't restore the original mac addresses on termination and will leave the mac address on the interface it was last on. Then, as ifdown is called on each slave it will hit a slave whose mac address has changed and is a dup of the other slave and it will hang there.
For some reason though if I set a programmable mac address not equal to any installed on the system on the bondX interfaces it complains the mac has changed, but it doesn't hang, so that is my interim work-around, set a unique MACADDR= on each bondX interface.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote:
Since I upgraded from 4.4 to 4.5 my system which has 2 sets of ALB bonded interfaces hangs on shutdown while doing an ifdown on these interfaces.
Has anyone else seen this issue with 4.5 and bonding?
I think I found the answer. The new version of bonding has a bug in it that doesn't restore the original mac addresses on termination and will leave the mac address on the interface it was last on. Then, as ifdown is called on each slave it will hit a slave whose mac address has changed and is a dup of the other slave and it will hang there.
For some reason though if I set a programmable mac address not equal to any installed on the system on the bondX interfaces it complains the mac has changed, but it doesn't hang, so that is my interim work-around, set a unique MACADDR= on each bondX interface.
can you report this as an issue at http://bugs.centos.org/ ?
- KB
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel-bounces@centos.org] On Behalf Of Karanbir Singh Sent: Thursday, May 31, 2007 4:39 PM To: The CentOS developers mailing list. Subject: Re: [CentOS-devel] RE: [CentOS] 4.5 ALB Bonding Hang on Shutdown [Bug]
Ross S. W. Walker wrote:
Since I upgraded from 4.4 to 4.5 my system which has 2 sets of ALB bonded interfaces hangs on shutdown while doing an ifdown on these interfaces.
Has anyone else seen this issue with 4.5 and bonding?
I think I found the answer. The new version of bonding has a bug in it that doesn't restore the original mac addresses on termination and will leave the mac address on the interface it was last on. Then, as ifdown is called on each slave it will hit a slave whose mac address has changed and is a dup of the other slave and it will hang there.
For some reason though if I set a programmable mac address not equal to any installed on the system on the bondX interfaces it complains the mac has changed, but it doesn't hang, so that is my interim work-around, set a unique MACADDR= on each bondX interface.
can you report this as an issue at http://bugs.centos.org/ ?
Will do.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.