Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Not really anything useful in them... Mar 8 12:09:42 retv3130 kernel: drbd: initialized. Version: 8.4.1 (api:1/proto:86-100) Mar 8 12:09:42 retv3130 kernel: drbd: GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by root at retv3130.na.lzb.hq, 2012-03-07 10:30:49 Mar 8 12:09:42 retv3130 kernel: drbd: registered as block device major 147 Mar 8 12:09:42 retv3130 kernel: d-con drbd0: Starting worker thread (from drbdsetup [7055]) Mar 8 12:09:42 retv3130 kernel: block drbd1: disk( Diskless -> Attaching ) Mar 8 12:09:42 retv3130 kernel: d-con drbd0: Method to ensure write ordering: barrier Mar 8 12:09:42 retv3130 kernel: block drbd1: max BIO size = 4096 Mar 8 12:09:42 retv3130 kernel: block drbd1: drbd_bm_resize called with capacity == 314554936 Mar 8 12:09:42 retv3130 kernel: block drbd1: resync bitmap: bits=39319367 words=614366 pages=1200 Mar 8 12:09:42 retv3130 kernel: block drbd1: size = 150 GB (157277468 KB) Mar 8 12:09:42 retv3130 kernel: block drbd1: bitmap READ of 1200 pages took 34 jiffies Mar 8 12:09:42 retv3130 kernel: block drbd1: recounting of set bits took additional 4 jiffies Mar 8 12:09:42 retv3130 kernel: block drbd1: 150 GB (39319367 bits) marked out-of-sync by on disk bit-map. Mar 8 12:09:42 retv3130 kernel: block drbd1: Suspended AL updates Mar 8 12:09:42 retv3130 kernel: block drbd1: disk( Attaching -> UpToDate ) Mar 8 12:09:42 retv3130 kernel: block drbd1: attached to UUIDs 1C6D2A54B80C1533:0000000000000004:0000000000000000:0000000000000000 Mar 8 12:09:42 retv3130 kernel: block drbd1: role( Secondary -> Primary ) Scot Kreienkamp skreien at la-z-boy.com -----Original Message----- From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Felix Frank Sent: Thursday, March 08, 2012 11:26 AM To: Scot Kreienkamp Cc: drbd-user Subject: Re: [DRBD-user] network startup failure On 03/08/2012 05:22 PM, Scot Kreienkamp wrote: > The disk is able to be mounted manually on the primary, but the two nodes will not talk to each other to sync up. Right, since drbdadm connect all fails as stated earlier. Are there relevant logs during the time this call fails? _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.