Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, I put this on-list again. On 05/17/2011 02:18 PM, Edwige Odedele wrote: > I have tried many things then I lost my DRBD connection between the both > nodes. What have you tried? lsof? fuser -m? > I just made " service drbd restart " on the second node. > > *After this my second node (Slave) show this:* > > > > Root2:~# cat /proc/drbd > > version: 8.3.7 (api:88/proto:86-91) > > GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root2, 2011- > > 05-04 10:47:00 > > 0: *cs:Unconnected ro:Secondary/Unknown ds:UpToDate/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* > > * * > > *and the first node (master) :* > > * * > > Root1:~# cat /proc/drbd > > version: 8.3.7 (api:88/proto:86-91) > > GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root1, 2011- > > 05-03 16:52:00 > > 0: *cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r----* > > ns:1816337748 nr:0 dw:3896420 dr:1812482849 al:1256 bm:110821 lo:0 > pe:0 ua:0 > > ap:0 ep:1 wo:b oos:92 > > * * > > *I have done:* > > drbdadm attach data > > drbdadm syncer data > > drbdadm connect data*, but no success.* > These look correct. You can use "drbd up" for short. Do it on the node that is Unconnected. Watch the kernel log (dmesg) for DRBD related errors if a connection is not made successfully. You may have produced split-brain. Regards, Felix