Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, On 04/02/2013 09:31 PM, Jared Harvey wrote: > The problem arises when I put the primary node to standby. The same > thing happens when I reboot, power off, or pull the plug. it actually works as designed. > /Master/Slave Set: ms_g_drbd/ > > / Slaves: [ hpsata02 ]/ > > / Stopped: [ g_drbd:0 ]/ > > / / > > On node 2 this is the DRBD status > > > > /root at HPSATA02:~# service drbd status/ > > /drbd driver loaded OK; device status:/ > > /version: 8.3.7 (api:88/proto:86-91)/ > > /srcversion: EE47D8BF18AC166BE219757/ > > /m:res cs ro ds p mounted > fstype/ > > /0:meta WFConnection Secondary/Unknown Outdated/DUnknown C/ > > /1:data WFConnection Secondary/Unknown Outdated/DUnknown C/ > DRBD is fully disabled on the standby/offline node, because setting a node to standby means "migrate all HA services away and stop them locally". In the DRBD case, this is not really what anybody wants (because your cluster enters a degraded state), but there is no workaround that I know of. Avoid the use of standby outside of actual maintenance periods. HTH, Felix