Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Martin what seems odd is the fact that one of your devices went into StandAlone mode. That should only happen in one of two cases: 1. Deliberate disconnect (drbdadm disconnect, or drbdadm attach without connect initially) 2. Split brain. If you just down the replication interface, the device on both nodes will go into NetworkFailure (transient) and then WFConnection. Upon reconnection, they will just go back into Connected mode. And no point should one of them become StandAlone. If that isn't working in your setup, please provide relevant config and log snippets for people to be able to help you out. Cheers, Florian On Tuesday 08 January 2008 10:53:52 Martin Gombac wrote: > No split brain. > > veliki ~ # dmesg | grep -i "split-brain" > veliki ~ # > mali ~ # dmesg | grep -i "split-brain" > mali ~ # > > On 2008.1.8, at 10:50, Florian Haas wrote: > > dmesg | grep -i "split-brain" > > > > hth, > > Florian > > > > On Tuesday 08 January 2008 10:46:51 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? > > -- : Florian G. Haas : LINBIT Information Technologies GmbH : Vivenotgasse 48, A-1120 Vienna, Austria