<div dir="auto"><div>Hi Kevin,<br><div class="gmail_extra"><br><div class="gmail_quote">On 27 Jan 2017 16:20, "Kevin Lemonnier" <<a href="mailto:lemonnierk@ulrar.net">lemonnierk@ulrar.net</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="elided-text">On Fri, Jan 27, 2017 at 02:45:46PM -0300, Gambit15 wrote:<br>
> Hey guys,<br>
> Would anyone be able to tell me the name/location of the gluster client<br>
> log when mounting through libgfapi?<br>
><br>
<br>
</div>Nowhere, unfortunatly. If you are talking about KVM (qemu) you'll get it<br>
on the stdout of the VM, which can be annoying to get depending on what<br>
you are using.<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">I'm using oVirt 4, which whilst backed by KVM, I'm aware has a few defaults which differ from pure KVM.</div><div dir="auto"><br></div><div dir="auto">On the gluster side, I'm running 3.8 in a (2+1)x2 setup & default server quorum settings.</div><div dir="auto"><br></div><div dir="auto">Basically, every now & then I notice random VHD images popping up in the heal queue, and they're almost always in pairs, "healing" the same file on 2 of the 3 replicate bricks.</div><div dir="auto">That already strikes me as odd, as if a file is "dirty" on more than one brick, surely that's a split-brain scenario? (nothing logged in "info split-brain" though)</div><div dir="auto"><br></div><div dir="auto">Anyway, these heal processes always hang around for a couple of hours, even when it's just metadata on an arbiter brick.</div><div dir="auto">That doesn't make sense to me, an arbiter shouldn't take more than a couple of seconds to heal!?</div><div dir="auto"><br></div><div dir="auto">I spoke with Joe on IRC, and he suggested I'd find more info in the client's logs...</div><div dir="auto"><br></div></div>