Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Florian, upgrading is not so easy on a productive system, but I think a found the problem. The console on the master said "drbd0: [smbd/8966] sock_sendmsg time expired, ko = 4294967295", 10 times or so. The 3ware controller of the slave reported no problem, even a verify was done without a problem. drbd0 lies on top of a Raid 5 with 5 disks. I checked all drives with smartcrl and one of the drives had a very high Raw_Read_Error_Rate. I replaced the hard drive, rebuilded the Raid and the problem was gone. Thanks, Arne Florian Haas wrote: > The DRBD version you are using is 4 releases behind the current (and final, > for the 0.7 branch) 0.7.25 version, which was released back in October. So > upgrade and see if your issue persists. If it does, give us your > drbd.conf, /proc/drbd from both hosts, and exact kernel version (uname -r). > Also, since your problem is "completely reproducible", I'm sure you'll have > no trouble detailing the _exact_ sequence of events which trigger your issue. > > Cheers, > Florian > > On Saturday 19 January 2008 16:30:54 Arne Altrichter wrote: >> Hi, >> >> we have 2 systems with DRBD. The DRBD sync is not active at the moment, >> because we are not able to resync the devices again. There is heavy >> traffic on the master via samba and nfs. The slave has about 350G data >> left to sync. >> [...] >