<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 25.09.2012 11:28, Lars Ellenberg
wrote:<br>
</div>
<blockquote cite="mid:20120925092839.GA8143@soda.linbit" type="cite">
<pre wrap="">On Sun, Sep 23, 2012 at 12:18:57PM +0200, Markus Müller wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello DRBD Users,
I have a drbd two-node setup running, and got alarmed by the LINBIT
mail about sync problems with newer kernels. So I updated to 8.4.2
and tried to make sure anything is fine now.
Even if the mail of LINBIT says that no action is required after
upgrading, I tried the "drbdadm verify" feature. And it found "oos",
means blocks not in sync. I thought okay, good that you thought for
that, and tried to fix this as described in the LINBIT mail by doing
"drbdadm disconnect/connect". It synced the found "oos:" and I
thought everything is fine, so I did rerun the "drbdadm verify" to
just be sure. And I saw... just found more "oos:"! I did again a
"drbdadm disconnect/connect" but there were still more "oos:" after
the next "drbdadm verify". I made this some loops and saw that this
is not working at all to fix this!
</pre>
</blockquote>
<pre wrap="">If this is while the device was idle,
it is an indication that your hardware flips bits.
If it happens while the device is in use,
certain usage patterns can cause blocks to be different,
search for "digest integrity explained" in the list archives.</pre>
</blockquote>
drbd has been stopped by setting from primary to secondary mode on
the primary, and then I run "drbdadm down" on both nodes. Then I
flushed kernel cache (echo 3 > /proc/sys/vm/drop_caches) o<span
style="color: rgb(34, 34, 34); font-family: arial, sans-serif;
font-size: small; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 16px;
orphans: 2; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); display: inline !important;
float: none; ">n both sides and made a new nbd server on and a new
nbd client.</span><br>
<br>
I've tested this hardware very well -> it HAD and HAS no problems
without the drbd module!<br>
<br>
I don't think its an good idear to reject verifiable bugs by
insinuate buggy hardware!!!<br>
<br>
LINBIT already found bugs with new kernels, it just seems that there
are some more than thought; and I have bad news for you: I
reactivated the array yesterday, used it, and deactivated it today
again and there is NEW INCONSISTENCY:<br>
<br>
Run of yesterday:<br>
<br>
root@as1:~# perl /root/diff.pl<br>
1 bad 101.656 GB<br>
2 bad 101.657 GB<br>
3 bad 102.018 GB<br>
4 bad 102.019 GB<br>
5 bad 107.151 GB<br>
6 bad 107.152 GB<br>
7 bad 111.034 GB<br>
8 bad 111.035 GB<br>
9 bad 131.833 GB<br>
10 bad 131.834 GB<br>
11 bad 132.559 GB<br>
12 bad 132.56 GB<br>
13 bad 137.735 GB<br>
14 bad 137.736 GB<br>
15 bad 140.642 GB<br>
16 bad 140.643 GB<br>
17 bad 141.094 GB<br>
18 bad 141.095 GB<br>
19 bad 535.806 GB<br>
20 bad 535.807 GB<br>
21 bad 556.083 GB<br>
22 bad 566.681 GB<br>
23 bad 599.43 GB<br>
24 bad 619.899 GB<br>
root@as1:~#<br>
<br>
Run of today:<br>
<br>
root@as1:~# perl diff.pl<br>
1 bad 66.044 GB<br>
2 bad 79.641 GB<br>
3 bad 82.567 GB<br>
4 bad 82.57 GB<br>
5 bad 82.578 GB<br>
6 bad 82.593 GB<br>
7 bad 111.034 GB<br>
8 bad 111.035 GB<br>
9 bad 123.787 GB<br>
10 bad 123.788 GB<br>
11 bad 131.833 GB<br>
12 bad 131.834 GB<br>
13 bad 132.559 GB<br>
14 bad 132.56 GB<br>
15 bad 139.435 GB<br>
16 bad 139.436 GB<br>
17 bad 140.664 GB<br>
18 bad 140.665 GB<br>
19 bad 149.93 GB<br>
20 bad 149.938 GB<br>
21 bad 198.326 GB<br>
22 bad 217.039 GB<br>
23 bad 217.042 GB<br>
24 bad 217.044 GB<br>
25 bad 217.045 GB<br>
26 bad 217.049 GB<br>
27 bad 249.926 GB<br>
28 bad 265.254 GB<br>
29 bad 265.255 GB<br>
30 bad 284.159 GB<br>
31 bad 284.164 GB<br>
32 bad 284.17 GB<br>
33 bad 284.172 GB<br>
34 bad 295.717 GB<br>
35 bad 295.718 GB<br>
36 bad 378.504 GB<br>
37 bad 378.506 GB<br>
38 bad 378.508 GB<br>
39 bad 399.445 GB<br>
40 bad 416.755 GB<br>
41 bad 528.304 GB<br>
42 bad 528.311 GB<br>
43 bad 528.312 GB<br>
44 bad 528.313 GB<br>
45 bad 528.314 GB<br>
46 bad 528.315 GB<br>
47 bad 528.321 GB<br>
48 bad 528.322 GB<br>
49 bad 528.335 GB<br>
root@as1:~# <br>
<br>
It seems that I have now different and more inconsistency! This is
absolutely inacceptable.<br>
<br>
</body>
</html>