<div>Hello,</div><div><br></div>The machine just use drbd device for some services but not all. Also it uses the disks dedicated to it - if that disk causes IO error for example, other disk might be still OK for all other services.<div>
<br></div><div>There are many uses scenarios of drbd which is not good to say: if drbd device got error, shutdown or reboot .</div><div><br></div><div>I think the better approach would be to disable drbd on it - the service/app using it will get IO error but that is it. (it might cause machine to be in high IO wait load, etc.., but this would be picked up by nagios and admin will check and then act upon it- that is better and more controllable way). </div>
<div><br></div><div>I know the event handler is meant to suit everybody's need but the default behavior should not do like that - to save some unexpected surprises. </div><div><br></div><div>cheers<br><br><div class="gmail_quote">
On Wed, Nov 30, 2011 at 8:04 PM, Felix Frank <span dir="ltr"><<a href="mailto:ff@mpexnet.de">ff@mpexnet.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class="im"><br>
On 11/30/2011 12:09 AM, Steve Kieu wrote:<br>
> Even if IO error you may not want to halt the whole machine - best thing<br>
> probably is to disabled/remove the drbd resource in question rather than<br>
> kill the machine.<br>
<br>
</div>that's assuming that the kernel can just "remove" a device in any given<br>
situation, which normally (from my experience) isn't the case.<br>
<br>
Furthermore, if your Primary is the Sync Target, i.e. its local disk is<br>
inconsistent, and it loses the connection to the UpToDate data, then<br>
there is no sane way that DRBD can treat an incoming write request.<br>
<br>
That's why you typically want a reboot, as nothing good can come from an<br>
inconsistent standalone primary.<br>
<br>
HTH,<br>
<font color="#888888">Felix<br>
</font></blockquote></div><br><br clear="all"><div><br></div>-- <br>Steve Kieu<br>
</div>