Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 06/12/2017 09:39 AM, Julien Escario wrote: > 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. > > [...] > > It would be really nice to get back to normal without a reboot. Any advice ? Force-disconnecting and/or firewalling the ports of all DRBD resources sometimes unblocks stuck kernel threads, but if even that does not help, then there is virtually no way to recover from a stuck kernel without rebooting it (well, maybe with a kernel debugger there would be, but that's a rather theoretical possibility). -- Robert Altnoeder +43 1 817 82 92 0 robert.altnoeder at linbit.com LINBIT | Keeping The Digital World Running DRBD - Corosync - Pacemaker f / t / in / g+ DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.