Am 26.11.2014 14:27, schrieb Lars Ellenberg:
DRBD "logging" is simply a printk.
Whether or not that makes it to stable storage via some syslog channel
or not is no longer in control of DRBD.
Especially if the storage in fact *did* have problems, I think it is
very unlikely that any logging would
On Wed, Nov 26, 2014 at 11:26:13AM +0100, Felix Zachlod wrote:
> I am currently investigating a problem with one drbd peer.
>
> We are runnung 8.4.5 on this and had configured disk-timeout 300 in
> global-properties.
>
> On Monday I observed a failing primary but could not see any hints
> for the
I am currently investigating a problem with one drbd peer.
We are runnung 8.4.5 on this and had configured disk-timeout 300 in
global-properties.
On Monday I observed a failing primary but could not see any hints for
the reason.
Today I saw this in the log file:
Nov 26 07:56:33 philippus-a
