Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Jun 12, 2017 at 09:39:08AM +0200, Julien Escario wrote: > Le 09/06/2017 à 14:24, Julien Escario a écrit : > > Le 09/06/2017 à 09:59, Robert Altnoeder a écrit : > >> On 06/08/2017 04:14 PM, Julien Escario wrote: > >>> Hello, > >>> A drbdmanage cluster is actually stuck in this state : > >>> .drbdctrl role:Secondary > >>> volume:0 disk:UpToDate > >>> volume:1 disk:UpToDate > >>> vm4 connection:NetworkFailure > >>> vm7 role:Secondary > >>> volume:0 replication:WFBitMapS peer-disk:Inconsistent > >>> volume:1 peer-disk:Outdated > >>> [...] > >>> Any way to restart this ressource without losing all other ressources ? > >> on vm4 and vm7, try 'drbdadm down .drbdctrl' followed by 'drbdadm up > >> .drbdctrl'. > >> In most cases, it just reconnects and fixes itself. > > [Sorry for the double post] > > Finally, I've been able to fully restore vm4 and vm5 (drbdsetup and drbdmanage > working) but not vm7. > > I've done that by firewalling port 6999 (port used by .drbdctrl ressource) and > issuing a down/up on drbdctrl on vm4 and vm5. > > So far, so good. > > It seems to be the pure drbd part is somewhat screwed on vm7. I can't issue any > drbdadm/drbdsetup command. They all hang up and keep running without being > killed by time or kill (even -9). > > With strace, drbdsetup status output is as the attached file. It seems to hang > while writing to a socket but I'm not really familiar with strace output. > > It would be really nice to get back to normal without a reboot. Any advice ? Without access to that machine, I'd say that is how you have to resolve it (reboot). And yes, we also saw these hangs in old drbd9 versions. Please do yourself a favor and update to a recent version of the whole DRBD stack. All the version information I saw in that thread is scary... Regards, rck