<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello Guys,<br>
I'm running DRBD 8.0.2 compiled on Centos5.<br>
<br>
I realised my iSCSI target exporting a chunk of a drbd device was
timeouting because I was too optimistic and had the<br>
syncer - rate variable too big (an easy mistake to make :-)<br>
<br>
After I set the syncer to { rate 5M; } and restarted drbd on both ends,
I could see many of these asserts in my log:<br>
<br>
<tt>Apr 24 09:14:47 nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt) ) in
/usr/src/drbd-8.0.2/drbd/drbd_actlog.c:840<br>
Apr 24 09:14:47 nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt)>=0 ) in
/usr/src/drbd-8.0.2/drbd/drbd_int.h:1768<br>
Apr 24 09:14:47 nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt) ) in
/usr/src/drbd-8.0.2/drbd/drbd_actlog.c:840<br>
Apr 24 09:14:47 nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt)>=0 ) in
/usr/src/drbd-8.0.2/drbd/drbd_int.h:1768<br>
Apr 24 09:15:18 nas02 last message repeated 3938 times<br>
Apr 24 09:16:19 nas02 last message repeated 10578 times<br>
</tt><br>
<br>
drbd22 is a device which was in the middle of sync of 700 GB<br>
<tt>( <b># drbdadm -- --overwrite-data-of-peer primary drbd22</b> )</tt><br>
at the moment I changed the rate to 5M and reloaded the drbd driver.
I'm getting these errors on the receiver side.<br>
<br>
When I pause the sync (<tt># drbdadm pause-sync drbd22</tt>), no more
ASSERTs are happening:<br>
<br>
<tt>Apr 24 09:32:35 nas02 last message repeated 11129 times<br>
Apr 24 09:32:36 nas02 last message repeated 116 times<br>
Apr 24 09:32:36 nas02 kernel: drbd22: conn( SyncTarget ->
PausedSyncT ) user_isp( 0 -> 1 ) <br>
Apr 24 09:32:36 nas02 kernel: drbd22: Resync suspended<br>
Apr 24 09:32:36 nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt)>=0 ) in
/usr/src/drbd-8.0.2/drbd/drbd_int.h:1768<br>
Apr 24 <b>09:46:00 </b>nas02 last message repeated 193 times<br>
Apr 24 <b>09:46:00</b> nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt)>=0 ) in
/usr/src/drbd-8.0.2/drbd/drbd_int.h:1768<br>
Apr 24 <b>09:46:00</b> nas02 kernel: drbd22: conn( PausedSyncT ->
SyncTarget ) user_isp( 1 -> 0 ) <br>
Apr 24 <b>09:46:00</b> nas02 kernel: drbd22: <b>Syncer continues</b>.<br>
Apr 24 <b>09:46:00</b> nas02 kernel: drbd22: ASSERT(
atomic_read(&mdev->local_cnt)>=0 ) in
/usr/src/drbd-8.0.2/drbd/drbd_int.h:1768<br>
Apr 24 09:46:31 nas02 last message repeated 6049 times</tt><br>
<br>
<tt><br>
</tt>No other drbd device has this ASSERT problem - just this one which
has been syncing (and will be for another 10 hours or so):<br>
<tt><br>
[root@nas02 ~]# cat /proc/drbd<br>
12: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---<br>
ns:25453040 nr:56543428 dw:81996468 dr:760980 al:66950 bm:180 lo:0
pe:0 ua:0 ap:0<br>
resync: used:0/31 hits:16157 misses:181 starving:0 dirty:0
changed:181<br>
act_log: used:0/127 hits:6296310 misses:467456 starving:0
dirty:400506 changed:66950<br>
13: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---<br>
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0<br>
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0<br>
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0<br>
<br>
21: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---<br>
ns:2483760 nr:4262560 dw:6746320 dr:2034212 al:2772 bm:37 lo:0 pe:0
ua:0 ap:0<br>
resync: used:0/31 hits:421 misses:37 starving:0 dirty:0
changed:37<br>
act_log: used:0/127 hits:618168 misses:5873 starving:0
dirty:3101 changed:2772<br>
<b>22: cs:SyncTarget st:Secondary/Secondary ds:Inconsistent/UpToDate C
r---<br>
ns:0 nr:568101024 dw:568101024 dr:0 al:0 bm:34674 lo:-76 pe:0 ua:0
ap:0<br>
[================>...] sync'ed: 82.8% (115912/670698)M<br>
finish: 6:46:29 speed: 4,836 (5,408) K/sec<br>
resync: used:0/31 hits:35471639 misses:34675 starving:0 dirty:0
changed:34675<br>
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0</b><br>
<br>
31: cs:Connected st:Secondary/Secondary ds:UpToDate/UpToDate C r---<br>
ns:681015616 nr:0 dw:0 dr:681015616 al:0 bm:41888 lo:0 pe:0 ua:0
ap:0<br>
resync: used:0/31 hits:42521852 misses:41624 starving:0 dirty:0
changed:41624<br>
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0</tt><br>
<br>
<tt><br>
<br>
global {<br>
usage-count no;<br>
}<br>
<br>
common {<br>
syncer { rate 10M; }<br>
}<br>
</tt><br>
<br>
<tt><b>resource drbd22</b> {<br>
protocol C;<br>
startup { wfc-timeout 0; degr-wfc-timeout 120; }<br>
disk { on-io-error detach; }<br>
net { timeout 60; connect-int 10; ping-int 10;<br>
max-buffers 2048; max-epoch-size 2048; }<br>
<br>
syncer { rate 5M; }<br>
<br>
on nas01.per.pt {<br>
device /dev/drbd22;<br>
disk /dev/sdc2;<br>
address 10.9.18.116:7795;<br>
meta-disk internal;<br>
}<br>
<br>
on nas02.nsw.pt {<br>
device /dev/drbd22;<br>
disk /dev/sdc2;<br>
address 10.9.18.216:7795;<br>
meta-disk internal;<br>
}<br>
</tt>}<br>
<br>
<br>
<br>
Any hints? Should I be worried about the ASSERT?<br>
I'm happy to provide more details.<br>
<br>
Thank you!<br>
Marji<br>
<br>
</body>
</html>