Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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 can you unconfigure the working resources? Failing that, have you tried forcefully removing the drbd module? Rebooting the secondary machine? Are there any other logs pertaining the frozen resource? Regards, Felix