Package: drbd8-utils
Version: 2:8.3.13-2
Severity: important
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages drbd8-utils depends on:
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-38+deb7u4
Versions of packages drbd8-utils recommends:
ii heirloom-mailx [mailx] 12.5-2
Versions of packages drbd8-utils suggests:
pn heartbeat <none>
-- Configuration Files:
/etc/drbd.conf changed [not included]
/etc/drbd.d/global_common.conf [Errno 13] Permission denied:
u'/etc/drbd.d/global_common.conf'
-- no debconf information
In the last versions of debian 6.x the resouce can has high syncer rate
The new version if you put more than 30% of the network bandwidth and
send a verifcation of a sync drbd fails with the error:
Sep 7 03:14:43 servidorup1 kernel: [17480.223197] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967295
Sep 7 03:14:49 servidorup1 kernel: [17486.220589] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967294
Sep 7 03:14:55 servidorup1 kernel: [17492.217804] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967293
Sep 7 03:15:01 servidorup1 kernel: [17498.215133] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967292
Sep 7 03:15:07 servidorup1 kernel: [17504.212565] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967291
Sep 7 03:15:13 servidorup1 kernel: [17510.209821] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967290
Sep 7 03:15:19 servidorup1 kernel: [17516.207213] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967289
Sep 7 03:15:25 servidorup1 kernel: [17522.204440] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967288
Sep 7 03:15:31 servidorup1 kernel: [17528.201863] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967287
Sep 7 03:15:37 servidorup1 kernel: [17534.199188] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967286
Sep 7 03:15:43 servidorup1 kernel: [17540.196513] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967285
Sep 7 03:15:49 servidorup1 kernel: [17546.193831] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967284
Sep 7 03:15:55 servidorup1 kernel: [17552.191160] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967283
Sep 7 03:16:01 servidorup1 kernel: [17558.188482] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967282
Sep 7 03:16:07 servidorup1 kernel: [17564.185807] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967281
Sep 7 03:16:13 servidorup1 kernel: [17570.183131] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967280
Sep 7 03:16:19 servidorup1 kernel: [17576.180454] block drbd0:
[drbd0_worker/5379] sock_sendmsg time expired, ko = 4294967279
the server must rebooted to solve the issue.
This don't fails in the Debian 6.0 (drbd: initialized. Version: 8.3.7
(api:88/proto:86-91))
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
