Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Jan 29, 2009 at 04:24:03PM +0100, Rainer Sabelka wrote:
> Hi,
>
> on a pair of Debian etch server (kernel 2.6.22-4-686) I'm using DRBD 8.0.12
> (from the backports repository).
>
> Yesterday I noticed that DRBD disconnected and went into StandAlone state and
> I have no clue why this happened.
> Below I'll include the relevant part of the syslog on both servers and my
> drbd.conf.
> Does anyone have an idea what happened?
> Could this have been caused by a network disruption?
to _me_, this looks like someone on server1 said "drbdadm disconnect"...
I may be wrong, of course.
> Why din't DRBD reconnect?
if I'm right: because someone told it not to.
> Thanks for all your help!
>
> -Rainer
>
>
> On server2 (which ran as primary)
>
> Jan 27 19:18:09 server2 kernel: drbd0: Writing meta data super block now.
> Jan 27 19:18:09 server2 kernel: drbd0: Creating new current UUID
> Jan 27 19:18:09 server2 kernel: drbd0: Writing meta data super block now.
> Jan 27 19:18:09 server2 kernel: drbd0: asender terminated
> Jan 27 19:18:09 server2 kernel: drbd0: Terminating asender thread
> Jan 27 19:18:09 server2 kernel: drbd0: tl_clear()
> Jan 27 19:18:09 server2 kernel: drbd0: Connection closed
> Jan 27 19:18:09 server2 kernel: drbd0: conn( TearDown -> Unconnected )
> Jan 27 19:18:09 server2 kernel: drbd0: receiver terminated
> Jan 27 19:18:09 server2 kernel: drbd0: receiver (re)started
> Jan 27 19:18:09 server2 kernel: drbd0: conn( Unconnected -> WFConnection )
> Jan 27 19:18:15 server2 kernel: drbd0: conn( WFConnection -> Disconnecting )
> Jan 27 19:18:15 server2 kernel: drbd0: Discarding network configuration.
> Jan 27 19:18:15 server2 kernel: drbd0: tl_clear()
> Jan 27 19:18:15 server2 kernel: drbd0: Connection closed
> Jan 27 19:18:15 server2 kernel: drbd0: conn( Disconnecting -> StandAlone )
> Jan 27 19:18:15 server2 kernel: drbd0: receiver terminated
> Jan 27 19:18:15 server2 kernel: drbd0: Terminating receiver thread
>
> ... and on server1 (secondary):
>
> Jan 27 19:18:09 server1 kernel: drbd0: peer( Primary -> Unknown ) conn(
> Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )
> Jan 27 19:18:09 server1 kernel: drbd0: short read receiving data: read 3840
> expected 4096
> Jan 27 19:18:09 server1 kernel: drbd0: error receiving Data, l: 4120!
> Jan 27 19:18:09 server1 kernel: drbd0: asender terminated
> Jan 27 19:18:09 server1 kernel: drbd0: Terminating asender thread
> Jan 27 19:18:09 server1 kernel: drbd0: Writing meta data super block now.
> Jan 27 19:18:09 server1 kernel: drbd0: tl_clear()
> Jan 27 19:18:09 server1 kernel: drbd0: Connection closed
> Jan 27 19:18:09 server1 kernel: drbd0: conn( Disconnecting -> StandAlone )
> Jan 27 19:18:09 server1 kernel: drbd0: receiver terminated
> Jan 27 19:18:09 server1 kernel: drbd0: Terminating receiver thread
>
>
> ---- drbd.conf ----
>
> common {
> syncer { rate 100M; }
> }
>
> resource drbd_data {
> protocol C;
>
> startup {
> # wfc-timeout 600;
> degr-wfc-timeout 120;
> }
>
> disk {
> on-io-error detach;
> }
>
> net {
> after-sb-0pri disconnect;
> after-sb-1pri disconnect;
> after-sb-2pri disconnect;
> rr-conflict disconnect;
> ko-count 20;
> }
>
> syncer {
> rate 100M;
> al-extents 257;
> }
>
> on server1 {
> device /dev/drbd0;
> disk /dev/sda7;
> address 10.43.101.111:7788;
> meta-disk internal;
> }
>
> on server2 {
> device /dev/drbd0;
> disk /dev/sda7;
> address 10.43.101.112:7788;
> meta-disk internal;
> }
> }
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed