<div dir="ltr">On Thu, Jul 25, 2013 at 5:52 AM, Marcus Bointon <span dir="ltr"><<a href="mailto:marcus@synchromedia.co.uk" target="_blank">marcus@synchromedia.co.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is a silly chicken-and-egg problem. I've found when I issue a reboot on a server that's mounted its own gluster volume via NFS (with the 'hard' option set),</blockquote>
<div><br></div><div>Mounting NFS export from localhost is a recipe for disaster for many other reasons (including deadlocks under heavy IO).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
it stops gluster before unmounting volumes. This causes the NFS client to hang waiting for a response from the gluster server (which will never happen because it's stopped), blocking the reboot, leaving the server hanging indefinitely. The only way out seems to be to power-cycle the server.<br>
<br>
How is this supposed to work? Is there some way of scheduling unmounts before killing gluster?<br></blockquote><div><br></div><div> Not sure about this - should the init.d shutdown script be de-prioritized for your runlevel? But then, we are talking about a use case which is highly non-recommended.<br>
</div><div><br></div><div>Avati</div></div></div></div>