Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Madison Kelly wrote: > > ------------------------------------------------ > global { > usage-count yes; > } > common { > protocol C; > syncer { rate 33M; } > } > resource r0 { > device /dev/drbd0; > meta-disk internal; > net { > allow-two-primaries; > } > startup { > become-primary-on both; > } > on an_san01 { > address 10.0.0.71:7789; > disk /dev/san01/lv02; > } > on an_san02 { > address 10.0.0.72:7789; > disk /dev/san02/lv02; > } > } > ------------------------------------------------ > > ------------------------------------------------ > [root at san01 ~]# drbdadm dump > WARN: no normal resources defined for this host (san01.alteeve.com)!? > > [root at san02 ~]# drbdadm dump > WARN: no normal resources defined for this host (san02.alteeve.com)!? > ------------------------------------------------ > > Can someone twack me with a clue-stick? :) > sure. i'll take a whack. :) trimming your email to the important parts i see. i'm pretty sure the problem is that in your config file you specify the hosts as an_san01 and an_san02 but drbd sees the hosts as san01 and san02. not exactly the same hostnames. according to the man page for drbd.conf, the 'on' option needs to match the output of uname -n. i'm guessing you created aliases to point an_san{01,02} to san{01,02} but drbd doesn't check them. change the config file to use the other names and you should be fine. mike