> Lars Ellenberg suggested that the problem was due to a bad > NIC. Maybe... but what are the odds that two different > systems have a bad NIC?
But it doesn't take two bad NICs, just a bad NIC at one end of the DRBD link. I note that you said... > > The DRBD traffic goes over a single Ethernet cable that > connects the two systems. This issue is rather close to my heart, since it just happened to me two weeks ago. A cluster that was working fine for over a year suddenly started acting up because the NIC at one end of the DRBD link went bad. I suggest you disconnect the DRBD resource temporarily (to get replication traffic off the link) and try a bunch of iperfs from the primary to the secondary. Be sure to enter the IP for the DRBD link. You should consistently get about 930mbps. If you get wildly diverging results, you probably have a flaky NIC at one end. -- Eric Robinson Disclaimer - March 5, 2011 This email and any files transmitted with it are confidential and intended solely for William Seligman,[email protected]. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
