Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
This is the log output of the primary (8.3.7) which is the sync source [426929.295891] block drbd1: Handshake successful: Agreed network protocol version 91 [426929.296233] block drbd1: Peer authenticated using 20 bytes of 'sha1' HMAC [426929.296249] block drbd1: conn( WFConnection -> WFReportParams ) [426929.296275] block drbd1: Starting asender thread (from drbd1_receiver [14699]) [426929.296572] block drbd1: data-integrity-alg: <not-used> [426929.296580] block drbd1: max_segment_size ( = BIO size ) = 65536 [426929.296590] block drbd1: drbd_sync_handshake: [426929.296593] block drbd1: self B2E75D9367A1C71B:41B5C01D5EDD0915:6F31928B8C7C4278:7E2AA5F059F1D9D5 bits:131070228 flags:0 [426929.296595] block drbd1: peer 41B5C01D5EDD0914:0000000000000000:0000000000000000:0000000000000000 bits:131070228 flags:0 [426929.296598] block drbd1: uuid_compare()=1 by rule 70 [426929.296599] block drbd1: Becoming sync source due to disk states. [426929.296602] block drbd1: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) [426929.646334] block drbd1: conn( WFBitMapS -> SyncSource ) [426929.646347] block drbd1: Began resync as SyncSource (will sync 524280912 KB [131070228 bits set]). [426929.703228] block drbd1: /var/lib/dkms/drbd8/8.3.7/build/drbd/drbd_receiver.c:1995: sector: 128s, size: 65536 [426929.719913] block drbd1: error receiving RSDataRequest, l: 24! [426929.728258] block drbd1: peer( Secondary -> Unknown ) conn( SyncSource -> ProtocolError ) [426929.728373] block drbd1: asender terminated [426929.728379] block drbd1: Terminating asender thread [426929.736571] block drbd1: Connection closed [426929.736577] block drbd1: conn( ProtocolError -> Unconnected ) [426929.736582] block drbd1: receiver terminated [426929.736584] block drbd1: Restarting receiver thread [426929.736586] block drbd1: receiver (re)started the nodes are connect via a cross private ip gigabit connection. without lvm or software raid yves On 12.06.2012, at 09:05, Felix Frank wrote: > On 06/12/2012 07:15 AM, y at yas.ch wrote: >> sock was shut down by peer >> meta connection shut down by peer. >> peer( Primary -> Unknown ) conn( SyncTarget -> BrokenPipe ) pdsk( >> UpToDate -> DUnknown ) > > Disconcerting. > > What does the log on the peer say? Hopefully it presents a reason for > shutting down the connection. > > Maybe your new kernel has a new NIC driver that bugs out on your > hardware? Is replacing components an option? Can you use a different NIC > for the initial sync, perhaps? > > HTH, > Felix