There are two nodes B3 (master) and B6 as shown
below.
Primary Standby
+----------+ +-----------+
| | disk mirr | |
| N1|--------------|N1 |
| | heartbeat | |
Disk------| B3 | | B6 |------ Disk
| ttyS0 |--------------| ttyS0 |
| | heartbeat | |
| | | |
| N2 | | N2 |
+----------+ +-----------+
| |
| |
| |
| |
+------------------------------------------------+
|
|
|
+--------+
| |
| client |
| |
+--------+
Initially B3 is running the master and owns drbd0 as
master and things are fine.
I reboot B3 and ofcourse, B6 tries to take over the
drbd0 resource. But, the other side is not there the
connection is lost.
When B3 comes back, the drbd status indicates the
following on B3 and B6.
[root@B3 rshankar]# drbd status
version : 57
0: cs:WFConnection st:Secondary/Unknown ns:6 nr:8 dw:14 dr:54 of:0
[root@B6 rshankar]# drbd status
version : 57
0: cs:Unconfigured st:Secondary/Unknown ns:6 nr:8 dw:14 dr:54 of:0
When I explicitly restart on B6
[root@B6 rshankar]# drbd restart
Unloading DRBD module [ OK ]
Loading DRBD module [ OK ]
Configuring DRBD resource drbd0 [ OK ]
Waiting for DRBD resource drbd0 to resynchronize [ OK ]
things come back. It seems that to run drbd, you need to have
a reboot as soon as the heartbeat is lost?
A similar situation also happens when both machines are rebooted at
the same time and B6 comes up first and then B3 which is the designated
master.
Any suggestions how to remedy this ?
/etc/ha.d/ha.cf
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 1
deadtime 5
serial /dev/ttyS0
baud 19200
udpport 694
udp eth1
node B6
node B3
/etc/ha.d/haresources
#
B3 172.16.12.26 datadisk::drbd0 httpd
============================================
Ravi N Shankar
Broadband Access Systems.
8 Technology Drive
Westboro MA 01581
rshankar@basystems.com
LiveVoice: (508)870 2519
============================================
below.
Primary Standby
+----------+ +-----------+
| | disk mirr | |
| N1|--------------|N1 |
| | heartbeat | |
Disk------| B3 | | B6 |------ Disk
| ttyS0 |--------------| ttyS0 |
| | heartbeat | |
| | | |
| N2 | | N2 |
+----------+ +-----------+
| |
| |
| |
| |
+------------------------------------------------+
|
|
|
+--------+
| |
| client |
| |
+--------+
Initially B3 is running the master and owns drbd0 as
master and things are fine.
I reboot B3 and ofcourse, B6 tries to take over the
drbd0 resource. But, the other side is not there the
connection is lost.
When B3 comes back, the drbd status indicates the
following on B3 and B6.
[root@B3 rshankar]# drbd status
version : 57
0: cs:WFConnection st:Secondary/Unknown ns:6 nr:8 dw:14 dr:54 of:0
[root@B6 rshankar]# drbd status
version : 57
0: cs:Unconfigured st:Secondary/Unknown ns:6 nr:8 dw:14 dr:54 of:0
When I explicitly restart on B6
[root@B6 rshankar]# drbd restart
Unloading DRBD module [ OK ]
Loading DRBD module [ OK ]
Configuring DRBD resource drbd0 [ OK ]
Waiting for DRBD resource drbd0 to resynchronize [ OK ]
things come back. It seems that to run drbd, you need to have
a reboot as soon as the heartbeat is lost?
A similar situation also happens when both machines are rebooted at
the same time and B6 comes up first and then B3 which is the designated
master.
Any suggestions how to remedy this ?
/etc/ha.d/ha.cf
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 1
deadtime 5
serial /dev/ttyS0
baud 19200
udpport 694
udp eth1
node B6
node B3
/etc/ha.d/haresources
#
B3 172.16.12.26 datadisk::drbd0 httpd
============================================
Ravi N Shankar
Broadband Access Systems.
8 Technology Drive
Westboro MA 01581
rshankar@basystems.com
LiveVoice: (508)870 2519
============================================