On 31 July 2012 10:33, Felix Frank <span dir="ltr"><<a href="mailto:ff@mpexnet.de" target="_blank">ff@mpexnet.de</a>></span> wrote:<br><br>> What's bugging me a bit is the relatively high number of "out<br>
> of sync" blocks as reported by your second node. Are you<br>> absolutely certain that no VM has been started on this node<br>> since you've lost connectivity? For that matter, how certain<br>> are you about the exact time your nodes started diverging?<br>
> <br>> You may want to check your logs. If possible, you may want to<br>> copy your second node's data before syncing, just to be safe.<br>> <br><br>Hi Felix,<br><br>I did start one or two of the VMs on the second node initially. That's<br>
how I discovered that things had gone wrong. They did start but<br>gave horrendous errors and hung for half a minute at a time.<br><br>But for sure, there aren't any running now on the broken node. The<br>first node is running all of the VMs, quite smoothly fortunately.<br>
<br>So it's safe to assume that that was the point that the nodes started<br>to diverge, I believe. Certainly the second node has had the wrong IP<br>address on the NIC facing the storage since before I attempted to <br>
start any of the VMs.<br><br>Not sure I even can copy the second node's data - it's not<br>communicating with the storage at all. But I only need the first node's<br>data.<br><br>Thanks again,<br>James<br><br>