[DRBD-user] can drbd be made to detect that it has failed to write to the underlying device in a 'long time'?
Lars.Ellenberg at linbit.com
Wed Apr 14 00:53:04 CEST 2004
/ 2004-04-13 16:48:09 -0500
\ Todd Denniston:
> Darn, I was not doing anything using the disk at the time it had a problem
> today, and missed the slow spot.
> on a positive note, about 22 seconds into the secondaries Card dump (I think
> this is the time that the lockup starts) I got the following on the active
> Apr 13 15:36:23 foo kernel: drbd1: sock_sendmsg time expired on sock
> Apr 13 15:36:23 foo kernel: drbd1: no data sent since 10 ping intervals, peer
> seems knocked out: going to StandAlone.
> Apr 13 15:36:23 foo kernel: drbd1: Connection lost.
Thats what I expect.
> so was the 'ko count down' messages something that you might have added or
> fixed in 0.6.1?
Probably. Wait a minute ...
yes. made it more verbose and improved it later than 0.6.10
so what about an update to 0.6.12 ...
More information about the drbd-user