Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have been searching why my LVM can't deactivating but no success.
I have tried many things then I lost my DRBD connection between the both
nodes.
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.
Please,I need your help.
This is the kernel’s log of the node that shows “ Unconnected “
May 17 14:57:34 sd-XXXXX kernel: [1124558.113675] block drbd0: ASSERT FAILED
cstate = WFConnection, expected < WFConnection
May 17 14:57:34 sd-XXXXX kernel: [1124558.113876] block drbd0: Connection
closed
May 17 14:57:34 sd-XXXXX kernel: [1124558.113884] block drbd0: conn(
WFConnection -> Unconnected )
May 17 14:57:35 sd-XXXXX kernel: [1124559.111062] block drbd0: conn(
Unconnected -> WFConnection )
May 17 14:57:35 sd-XXXXX kernel: [1124559.203047] block drbd0: Handshake
successful: Agreed network protocol version 91
May 17 14:57:35 sd-XXXXX kernel: [1124559.203375] block drbd0: expected
AuthChallenge packet, received: ReportProtocol (0x000b)
May 17 14:57:35 sd-XXXXX kernel: [1124559.203380] block drbd0:
Authentication of peer failed, trying again.
May 17 14:57:35 sd-XXXXX kernel: [1124559.203384] block drbd0: ASSERT FAILED
cstate = WFConnection, expected < WFConnection
May 17 14:57:35 sd-XXXXX kernel: [1124559.203524] block drbd0: Connection
closed
May 17 14:57:35 sd-XXXXX kernel: [1124559.203532] block drbd0: conn(
WFConnection -> Unconnected )
May 17 14:57:36 sd-XXXXX kernel: [1124560.198077] block drbd0: conn(
Unconnected -> WFConnection )
What do you think the problem could be?
Or do I need to generate a new sshkeygen between the nodes?
How to to re-sync the configs?
Cordialement,
Edwige ODEDELE
Apprentie Réseaux et Sécurité
Work: +33 1 80 90 50 80
Direct: +33 1 80 90 50 88
Email: odedele at popsicube.fr
Fax: +33 1 80 90 50 89
POPSI CUBE
6 rue Jean-Pierre Timbaud – A1 Sud
78180 Montigny le Bretonneux
FRANCE
-----Message d'origine-----
De : Felix Frank [mailto:ff at mpexnet.de]
Envoyé : mardi 17 mai 2011 14:32
À : Edwige Odedele
Cc : drbd-user
Objet : Re: [DRBD-user] 0: State change failed: (-12) Device is held open by
someone
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110517/40145394/attachment.htm>