<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-09-19 10:50 GMT+02:00 Igor Cicimov <span dir="ltr"><<a href="mailto:igorc@encompasscorporation.com" target="_blank">igorc@encompasscorporation.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"></p>
<p dir="ltr"><span class="">On 19 Sep 2016 5:45 pm, "Marco Marino" <<a href="mailto:marino.mrc@gmail.com" target="_blank">marino.mrc@gmail.com</a>> wrote:<br>
><br>
> Hi, I'm trying to build an active/passive cluster with drbd and pacemaker for a san. I'm using 2 nodes with one raid controller (megaraid) on each one. Each node has an ssd disk that works as cache for read (and write?) realizing the CacheCade proprietary tecnology. <br>
><br></span>
Did you configure the CacheCade? If the write cache was enabled in write-back mode then suddenly removing the device from under the controller would have caused serious problems I guess since the controller expects to write to the ssd cache firts and then flush to the hdd's. Maybe this explains the read only mode?</p></blockquote><div>Good point. It is exactly as you wrote. How can I mitigate this behavior in a clustered (active/passive) enviroment??? As I told in the other post, I think the best solution is to poweroff the node using local-io-error and switch all resources on the other node.... But please give me some suggestions....<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr"><span class="">> Basically, the structure of the san is:<br>
><br>
> Physycal disks -> RAID -> Device /dev/sdb in the OS -> Drbd resource (that use /dev/sdb as backend) (using pacemaker with a master/slave resource) -> VG (managed with pacemaker) -> Iscsi target (with pacemaker) -> Iscsi LUNS (one for each logical volume in the VG, managed with pacemaker)<br>
><br>
> Few days ago, the ssd disk was wrongly removed from the primary node of the cluster and this caused a lot of problems: drbd resource and all logical volumes went in readonly mode with a lot of I/O errors but the cluster did not switched to the other node. All filesystem on initiators went to readonly mode. There are 2 problems involved here (I think): 1) Why removing the ssd disk cause a readonly mode with I/O errors? This means that the ssd is a single point of failure for a single node san with megaraid controllers and CacheCade tecnology..... and 2) Why drbd not worked as espected?<br></span>
What was the state in /proc/drbd ?</p></blockquote><div><br></div><div>Diskless<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr"><span class="">> For point 1) I'm checking with the vendor and I doubt that I can do something<br>
> For point 2) I have errors in the drbd configuration. My idea is that when an I/O error happens on the primary node, the cluster should switch to the secondary node and shut down the damaged node. <br>
> Here -> <a href="http://pastebin.com/79dDK66m" target="_blank">http://pastebin.com/79dDK66m</a> it is possible to see the actual drbd configuration, but I need to change a lot of things and I want to share my ideas here:<br>
><br>
> 1) The "handlers" section should be moved in the "common" section of global_common.conf and not in the resource file.<br>
><br>
> 2)I'm thinking to modify the "handlers" section as follow:<br>
><br>
> handlers { pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-<wbr>incon-degr.sh; /usr/lib/drbd/notify-<wbr>emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f"; pri-lost-after-sb "/usr/lib/drbd/notify-pri-<wbr>lost-after-sb.sh; /usr/lib/drbd/notify-<wbr>emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f"; local-io-error "/usr/lib/drbd/notify-io-<wbr>error.sh; /usr/lib/drbd/notify-<wbr>emergency-shutdown.sh; echo o > /proc/sysrq-trigger ; halt -f"; # Hook into Pacemaker's fencing. fence-peer "/usr/lib/drbd/crm-fence-peer.<wbr>sh"; }<br>
><br>
><br>
> In this way, when an I/O error happens, the node will be powered off and pacemaker will switch resources to the other node (or at least doesn't create problematic behaviors...)<br>
><br>
> 3) I'm thinking to move the "fencing" directive from the resource to the global_common.conf file. Furthermore, I want to change it to<br>
><br>
> fencing resource-and-stonith;<br>
><br>
><br>
> 4) Finally, in the global "net" section I need to add:<br>
><br>
> after-sb-0pri discard-zero-changes; after-sb-1pri discard-secondary; after-sb-2pri disconnect;<br>
><br>
> At the end of the work configuration will be -> <a href="http://pastebin.com/r3N1gzwx" target="_blank">http://pastebin.com/r3N1gzwx</a><br>
><br>
> Please, give me suggestion about mistakes and possible changes.<br>
><br>
> Thank you<br>
><br>
><br>
><br></span>
> ______________________________<wbr>_________________<br>
> drbd-user mailing list<br>
> <a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
> <a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/<wbr>mailman/listinfo/drbd-user</a><br>
></p>
</blockquote></div><br></div></div>