Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
All, I'm using DRBD 0.7.13 on Linux 2.4.30-xen0 and it has gone insane. Every one second for the past several hours (since the machine was rebooted after a kernel panic last night) both systems have been logging messages like: (one) Oct 14 13:50:04 cog-psi-1 kernel: drbd0: drbd0_receiver [776]: cstate Unconnected --> WFConnection Oct 14 13:50:05 cog-psi-1 kernel: drbd0: drbd0_receiver [776]: cstate WFConnection --> WFReportParams Oct 14 13:50:05 cog-psi-1 kernel: drbd0: sock was shut down by peer Oct 14 13:50:05 cog-psi-1 kernel: drbd0: drbd0_receiver [776]: cstate WFReportParams --> BrokenPipe Oct 14 13:50:05 cog-psi-1 kernel: drbd0: short read expecting header on sock: r=0 Oct 14 13:50:05 cog-psi-1 kernel: drbd0: worker terminated Oct 14 13:50:05 cog-psi-1 kernel: drbd0: drbd0_receiver [776]: cstate BrokenPipe --> Unconnected Oct 14 13:50:05 cog-psi-1 kernel: drbd0: Connection lost. (two) Oct 14 13:55:36 cog-psi-2 kernel: drbd0: drbd0_receiver [775]: cstate Unconnected --> WFConnection Oct 14 13:55:36 cog-psi-2 kernel: drbd0: drbd0_receiver [775]: cstate WFConnection --> WFReportParams Oct 14 13:55:36 cog-psi-2 kernel: drbd0: sock was shut down by peer Oct 14 13:55:36 cog-psi-2 kernel: drbd0: drbd0_receiver [775]: cstate WFReportParams --> BrokenPipe Oct 14 13:55:36 cog-psi-2 kernel: drbd0: worker terminated Oct 14 13:55:36 cog-psi-2 kernel: drbd0: drbd0_receiver [775]: cstate BrokenPipe --> Unconnected Oct 14 13:55:36 cog-psi-2 kernel: drbd0: Connection lost. Anyone have any ideas why DRBD has gone insane ? Roy Keene Planning Systems Inc