Hi
 
I am using DRBD (8.4.5) in dual primary mode (with GFS2) on Red Hat Enterprise Linux Server release 7.0 (Cluster, Pacemaker).
 
Everything workes fine only if a node crashes (i pull the power plug), the shared directory becomes unusable: for eg. a 'ls -l' blocks until the node has rebooted normally.
During this situation the drbd status for the second node is Unknown/Outdated.
 
I am using the configuration as supposed on the homepage.
 
Am i missing something ?
 
Another question: It is possible to define the time when an active node gets informed about another node crash (currently it takes about 2sec before DRBD changes the status of the crashed node) ?
 
thx
 
global_common.conf
-------------------------------
global {
 usage-count no;
}
common {
 handlers {
  fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
  after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
  split-brain "/usr/lib/drbd/notify-split-brain.sh root";
 }
 startup {
  wfc-timeout 300;
  degr-wfc-timeout 0;
  become-primary-on both;
 }
 options { }
 disk {
  resync-rate 100M;
  fencing resource-and-stonith;
 }
 net {
  protocol C;
 }
}
 
r0.res
-------------------------------
resource r0 {
 device    /dev/drbd1;
 disk      /dev/rhel/drbd;
 meta-disk internal;
        net {
  allow-two-primaries;
  after-sb-0pri discard-zero-changes;
  after-sb-1pri discard-secondary;
  after-sb-2pri disconnect;
 }
 on node1.localdomain {
  address   192.168.0.111:7789;
 }
 on node2.localdomain {
  address   192.168.0.113:7789;
 }
}
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to