Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, May 01, 2012 at 01:44:59AM +0800, Norman wrote: > Hi All, > > I'm new to the list. I don't deal with drbdadm all the time because > drbd just runs (usually). I've got a weird state with my drbd (2 > nodes). Everything was fine till, I shutdown my 'secondary' for a > few minutes just to re-seat a drive. > > Now, the Primary says... > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/Outdated r---- > ns:7478380 nr:12656820 dw:22139484 dr:17976297 al:52974 bm:12391 > lo:4 pe:0 ua:0 ap:3 ep:1 wo:b oos:795380 > > Secondary says... > > 1: cs:WFConnection ro:Secondary/Unknown ds:Outdated/DUnknown C r---- > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 In case you still need help... Go to the node that is "StandAlone", say "drbdadm -d adjust all" (-d for dry run) it should tell you that it is going to call "drbdsetup ... net ...", nothing about detach/attach or the like. If so, do "drbdadm adjust all" (without the -d this time). (btw, drbdadm connect all should have had the same effect here). if it still does not start to resync, look into the kernel logs, and if they are not obvious, post them here. (grep drbd1: /var/log/messages or .../kern.log or similar, dmesg | grep drbd1:, something like that.) > > Nothing really changed, both servers can ping each other via the > drbd channel. How do I get the servers connected again and the > 'secondary' to be 'UpToDate' again. Is it easily re-synced. Help > Please. > > Thanks, > Norman -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com