Hi,
Upon rebooting one of my machines (a cluster of two), everything seems to be right with DRBD re-sync. Nevertheless, after a noticeable (thorugh ping) network loss (a couple of seconds), one of the DRBD partitions (that already appeared as UpToDate) losses sync and I get a split brain. Following logs, it seems that network interfaces get up and ready and DRBD things start working. In the middle of the log it appears that network interfaces are dropped and brought up again. This then makes a split brain to appear because both machines have been running as Primary during the network loss.
So I was wondering if any of the PVE services (or corosync or whatever) is to blame for this temporary network loss and that If I should not start DRBD until everything related to networks is up and stable.
The runlevel I have is this:
README S17vzeventd S18postfix S19cman S20rgmanager S25nxserver
S14portmap S18acpid S18proftpd S19cpufrequtils S20saned S25pvebanner
S15nfs-common S18anacron S18pve-cluster S19cron S21pvedaemon S25rc.local
S17binfmt-support S18atd S18rsync S19drbd S21qemu-server S25rmnologin
S17fancontrol S18dbus S18snmpd S19gdm3 S21vz S25stop-bootlogd
S17ksmtuned S18exim4 S18ssh S20bootlogs S22apache2
S17rrdcached S18kerneloops S18sysstat S20clvm S23pvestatd
S17rsyslog S18loadcpufreq S19avahi-daemon S20cups S24pve-manager
S17sudo S18ntp S19bluetooth S20netperf S25nxsensor
Would you recommend me to move drbd to S26 (and stop-bootlogd to S27 to keep logs) ??? Could this make any harm?... or perhaps a less elegant way like adding some delay to the drbd init script??
Thanks in advance.
Jose
Upon rebooting one of my machines (a cluster of two), everything seems to be right with DRBD re-sync. Nevertheless, after a noticeable (thorugh ping) network loss (a couple of seconds), one of the DRBD partitions (that already appeared as UpToDate) losses sync and I get a split brain. Following logs, it seems that network interfaces get up and ready and DRBD things start working. In the middle of the log it appears that network interfaces are dropped and brought up again. This then makes a split brain to appear because both machines have been running as Primary during the network loss.
So I was wondering if any of the PVE services (or corosync or whatever) is to blame for this temporary network loss and that If I should not start DRBD until everything related to networks is up and stable.
The runlevel I have is this:
README S17vzeventd S18postfix S19cman S20rgmanager S25nxserver
S14portmap S18acpid S18proftpd S19cpufrequtils S20saned S25pvebanner
S15nfs-common S18anacron S18pve-cluster S19cron S21pvedaemon S25rc.local
S17binfmt-support S18atd S18rsync S19drbd S21qemu-server S25rmnologin
S17fancontrol S18dbus S18snmpd S19gdm3 S21vz S25stop-bootlogd
S17ksmtuned S18exim4 S18ssh S20bootlogs S22apache2
S17rrdcached S18kerneloops S18sysstat S20clvm S23pvestatd
S17rsyslog S18loadcpufreq S19avahi-daemon S20cups S24pve-manager
S17sudo S18ntp S19bluetooth S20netperf S25nxsensor
Would you recommend me to move drbd to S26 (and stop-bootlogd to S27 to keep logs) ??? Could this make any harm?... or perhaps a less elegant way like adding some delay to the drbd init script??
Thanks in advance.
Jose