[DRBD-user] Primary fully unavailable with "time expired" errors

AZ 9901 az9901 at gmail.com
Tue Mar 5 07:21:21 CET 2013

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

// I made some errors in my previous mail, here they are corrected


I faced a big issue with DRBD.

OS : Linux Debian 6
Kernel : 2.6.32-46
DRBD : 8.3.14

My primary server (srv2-2) was totally unreachable, it only replied to ping.
Apache, SSH etc... were not replying anymore.

So I connected to my secondary server (srv2-1) and closed network communication between both.
This made srv2-2 available again !
I decided however to change srv2-1 from Secondary to Primary and to reboot srv2-2.

Following are logs from srv2-2 and srv2-1, with some comments.
srv2-2 : http://pastebin.com/raw.php?i=zkHV5Tr9
srv2-1 : http://pastebin.com/raw.php?i=WX4vNR6d

on srv2-2, sar tells me that some of my CPU cores were 100% used (100% iowait) during all the time frame in which I had "time expired" errors. 

Could you help me please ?

Thank you very much,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130305/0912ec7e/attachment.htm>

More information about the drbd-user mailing list