Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I experienced this behavior as well. A warning to Red Hat/CentOS users: If you do a "service network restart" on a server with an active DRBD connection, DRBD will go into StandAlone state on that server and will stay in that state until you manually reconnect. On Jan 8, 2008 3:35 AM, Martin Gombac <martin at isg.si> wrote: > On 2008.1.8, at 12:28, Lars Ellenberg wrote: > > > On Tue, Jan 08, 2008 at 10:46:51AM +0100, Martin Gombac wrote: > >> Hi, > >> > >> is DRBD supposed to reconnect automatically after network comes > >> back up? > >> > >> I did a test for my network status script and had to ifconfig eth3 > >> down for one day. > >> eth3 is used for drbd syncing. After i brought eth3 back up i > >> expected for drbd to resync data again without me > >> doing drbdadm connect all. Was i wrong? > > > > if drbd cannot bind the address it is configured to use, > > it gives up. it also logs that into the kernel log. > > you should have looked there. > > > > do "drbdadm adjust all", and it should recover. > > Like you said. > > drbd1: conn( Unconnected -> WFConnection ) > drbd1: Unable to bind source sock (-99) > drbd1: Unable to bind source sock (-99) > drbd1: Unable to bind source sock (-99) > drbd1: Unable to bind sock2 (-99) > drbd1: conn( WFConnection -> Disconnecting ) > drbd1: Discarding network configuration. > drbd1: tl_clear() > drbd1: Connection closed > drbd1: conn( Disconnecting -> StandAlone ) > > I used drdbadm connect all and it worked. > > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user >