Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> > > please do > > > # ps -eo pid,state,wchan:30,cmd | grep -e D -e drbd > > > > 171 S drbd_nl_disconnect [cqueue/1] > > 7735 S - [drbd0_worker] > > 13018 D drbd_disconnect [drbd0_receiver] > > 21135 S pipe_wait grep drbd > > to even start guessing about anything, > what I'd need is /proc/drbd (not only the first line), > and the above output, of both nodes, > when they are in this "hanging" state. I only have output of one node right now, the other one has been already rebooted. Hope that helps nevertheless. > cat /proc/drbd version: 8.0.8 (api:86/proto:86) GIT-hash: bd3e2c922f95c4fa0dca57a4f8c24bf8b249cc02 build by root at vmhost.private, 2008-01-02 21:11:11 0: cs:Disconnecting st:Secondary/Unknown ds:UpToDate/Inconsistent C r--- ns:1360172 nr:0 dw:49554716 dr:1364921 al:25388 bm:25544 lo:0 pe:0 ua:0 ap:0 resync: used:0/31 hits:679830 misses:89 starving:0 dirty:0 changed:89 act_log: used:0/19 hits:12363291 misses:26105 starving:3 dirty:716 changed:25388 > also, maybe you can trigger a sysrq shoW-blocked-tasks (or showTasks, if > your kernel does not have the former), and see if you can figure out > where exactly the drbd_disconnect sleeps, so we know what exactly it is > waiting for. Very good idea! However, have not used sysrq yet, and Documentation/sysrq.txt doesn't know about showtasks, so how do I do this, i.e. what do I write to /proc/sysrq-trigger? Walter -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail