We are having some issues with gfs2 and drbd. When both nodes are up things work great. I can access the file on both nodes and they are in primary/primary mode.<br><br>The issue is that if a node is down I cannot access the mount on the system that is up. I can only access it when the node comes back online. <br>
<br>I followed a howto at the following URL just used a bit different drbd.conf<br><br><a href="http://gfs.wikidev.net/DRBD_Cookbook">http://gfs.wikidev.net/DRBD_Cookbook</a><br><br><br>Below is my drbd.conf<br><br>global {<br>
usage-count no;<br>}<br><br>common {<br> syncer { rate 100M; }<br>}<br><br>resource "drbd0" {<br> protocol C;<br><br> handlers {<br> pri-on-incon-degr "echo 'DRBD: primary requested but inconsistent!' | wall; /etc/init.d/heartbeat stop"; #"halt -f";<br>
pri-lost-after-sb "echo 'DRBD: primary requested but lost!' | wall; /etc/init.d/heartbeat stop"; #"halt -f";<br> }<br><br> startup {<br> wfc-timeout 0; # 2 minutes<br>
degr-wfc-timeout 120; # 2 minutes.<br> become-primary-on both;<br> }<br><br> syncer {<br> rate 100M;<br> # This is now expressed with "after res-name"<br>
#group 1;<br> al-extents 257;<br> }<br><br> net {<br> allow-two-primaries;<br> after-sb-0pri discard-zero-changes;<br> after-sb-1pri discard-secondary;<br>
after-sb-2pri disconnect;<br><br> }<br><br> disk {<br> on-io-error pass_on;<br> fencing dont-care;<br> }<br><br><br> on <a href="http://njrh-testdfs1.fxserver.com">njrh-testdfs1.fxserver.com</a> {<br>
device /dev/drbd0;<br> disk /dev/hdb1;<br> address <a href="http://10.100.172.195:7788">10.100.172.195:7788</a>;<br> meta-disk internal;<br>
}<br><br> on <a href="http://njrh-testdfs2.fxserver.com">njrh-testdfs2.fxserver.com</a> {<br> device /dev/drbd0;<br> disk /dev/hdb1;<br> address <a href="http://10.100.172.196:7788">10.100.172.196:7788</a>;<br>
meta-disk internal;<br> }<br>}<br><br><br>