Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jan 16, 2013 at 03:57:33PM +0100, Felix Frank wrote: > Hi, > > On 01/11/2013 10:36 AM, Abdelkarim Mateos Sanchez wrote: > > Dec 31 17:52:31 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961767 > > Dec 31 17:52:37 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961766 > > Dec 31 17:52:43 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961765 > > Dec 31 17:52:49 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961764 > > Dec 31 17:52:55 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961763 > > Dec 31 17:53:01 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294961762 First of all, why not configure ko-count? e.g: ko-count 6; That should then starting to count from 6, and forcefully disconnect automatically once it hits zero. > can you unconfigure the working resources? Failing that, have you tried > forcefully removing the drbd module? Rebooting the secondary machine? ifconfig down; sleep 12; ifconfig up; or use iptables .... -j REJECT --reject-with tcp-reset Lars