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 have found the solution for my problem, I answer for person who have the same problem. My drbd shared space was uptodate on both node but were displayed in drbd in "consistent" mode and it can't be connected. The solution was to detach and invalidate shared space on one node an connect the two nodes for a re-sync [node1] drbdadm detach share [node1] drbdadm invalidate share [node1] drbdadm attach share [node1] drbdadm connect share [node2] drbdadm connect share Regards. -----Message d'origine----- De : drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] De la part de Baptiste Agasse Envoyé : jeudi 11 décembre 2008 16:55 À : drbd-user at lists.linbit.com Objet : [DRBD-user] Force one node to be uptodate Hi all, I have a problem after making ntp syncronisation of my 2 nodes cluster. Drbd shared device was in cs:Connected st:Primary/Primary ds:UpToDate/ UpToDate state,on both node. But after reboot, the first node state is : cs:StandAlone st:Secondary/Unknown ds:Consistent/DUnknown and second : cs:WFConnection st:Secondary/Unknown ds:Consistent/DUnknown Since that, I can't force one node to be in UpTopDate state in order to connect two nodes (drbd say : Refusing to be Primary without at least one UpToDate disk) Regards, PS: sorry for my bad English, thanks a lot for yoursd answers. _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user