Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2006-06-13 09:22:43 +0200 \ Gernot W. Schmied: > Lars Ellenberg wrote: > > / 2006-06-11 23:22:38 +0200 > > \ Gernot W. Schmied: > >> Hi, > >> > >> Since my migration (didn't change a thing!) to newest Ubuntu my DRBD > >> setup (0.7.17 on both machines) on my primary machine suddenly insists > >> to remain in "secondary" mode. Any idea why? > > > > well. > > what do you mean by "insist"? > > if you tell it to become primary, what exactly does happen? > > how do you try to do the "drbdadm primary all"? > > > > Hmm, the primary node so far always remained primary after setting it > once regardless of the secondary being reachable and it maintained that > state regardless of restarting drbd via /etc/init.d/drbd. > Now it always returns to secondary state when I stop/restart drbd after > declaring it primary with "drbdadm primary all" before mounting my file > systems. Maybe it is supposed to be that way but I'd like to understand > why. Why does it return to secondary state when I stop drbd? back to the original question... the drbd init script does not switch any drbd device to primary. never did. it just configures the drbd module. so it comes up as seconday. always been that way (for the 0.7 series at least). so what _did_ switch your devices primary before? where/how do you try to do the "primary all"? you did not answer that question yet. any chances it was a hand-crafted init script before, and the update replaced it with the distribution one? anyways, case closed, I think... -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client.