<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 23, 2012, at 3:45 PM, Lars Ellenberg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Wed, May 23, 2012 at 03:34:27PM -0500, Zev Weiss wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On May 23, 2012, at 3:22 PM, Florian Haas wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">On Wed, May 23, 2012 at 10:14 PM, Zev Weiss <<a href="mailto:zweiss@scout.wisc.edu">zweiss@scout.wisc.edu</a>> wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hi,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I'm running DRBD 8.3.12, and recently hit what looks to me like a bug that was listed as fixed in 8.3.13 -- getting into a state where both nodes are in SyncSource (it's just stuck like that, going nowhere). Luckily this happened on a test resource and not a live one, so it's not a big problem, but I was wondering if there were any known ways of recovering it without doing anything disruptive to the other resources (e.g. rebooting or unloading the kernel module).<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I've tried 'drbdadm down', but it just hangs -- anyone have any other suggestions? It doesn't really matter to me if it wipes the resource or anything, I'd just like to have my test device back in a working state without disturbing anything else.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Can you post /proc/drbd contents from both nodes here?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sure -- here's one node:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">version: 8.3.12 (api:88/proto:86-96)<br></blockquote><blockquote type="cite">GIT-hash: e2a8ef4656be026bbae540305fcb998a5991090f build by zweiss@mydomain, 2012-03-14 19:52:38<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><snip other resources><br></blockquote><blockquote type="cite"> 9: cs:SyncSource ro:Secondary/Primary ds:UpToDate/Inconsistent C r-----<br></blockquote><blockquote type="cite"> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:65536<br></blockquote><blockquote type="cite"> [>...................] sync'ed: 5.9% (65536/65536)K<br></blockquote><blockquote type="cite"> finish: 19046:04:53 speed: 0 (0 -- 0) K/sec (stalled)<br></blockquote><blockquote type="cite"> 0% sector pos: 0/10698352<br></blockquote><blockquote type="cite"> resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0<br></blockquote><blockquote type="cite"> act_log: used:0/3389 hits:0 misses:0 starving:0 dirty:0 changed:0<br></blockquote><br>drbdsetup 9 disconnect --force<br>may work,<br>if you did not try a non-forced disconnect or similar before,<br>that is to say, if the drbd worker thread is not blocked yet.<br><br></div></blockquote><div><br></div><div>I think I had tried a non-forced disconnect previously (and perhaps also implicitly as part of a 'down' attempt, though I'm not sure whether it would have gotten to that step if the disconnect operation didn't complete), but 'drbdsetup 9 disconnect --force' also just hangs.</div><br><blockquote type="cite"><div>You can always cut the tcp connection using iptables,<br>which should at least get the worker into a responsive state again.<br><font class="Apple-style-span" color="#007316"><br></font></div></blockquote></div><br><div>As mentioned in another message in response to Florian, blocking the replication port via iptables doesn't seem to have had any effect.</div><div><br></div><div><br></div><div>Thanks,</div><div>Zev</div><div><br></div></body></html>