Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jun 21, 2011 at 04:03:31PM -0600, Pete Ashdown wrote: > On 06/21/2011 03:55 PM, Lars Ellenberg wrote: > > On Tue, Jun 21, 2011 at 10:13:06AM -0600, Pete Ashdown wrote: > >> If a system properly shuts down drbd upon shutdown, then starts it up upon > >> reboot, I don't understand how there could be pending changes on it. > >> Shouldn't it just sync up to its peer and go? Instead I get split-brain > >> every time I reboot a node. What settings are required to just go > >> secondary, connect, sync, and then go primary upon reboot? > > First make "unused" (umount, typically). > > Then make secondary. > > > > Only then disconnect. > > > > If you disconnect (by for example shutting down the network) > > while both are still in Primary role, > > you get what you observe. > > > > Double check the kill script order, > > or equivalent. > Thank you Lars. > > If I make secondary with the kill script, will it come back as primary upon > reboot, or do I need to specifically insert that into the startup script? DRBD always comes up as Secondary, and will be made Primary by either the drbd init script, if you so chose, or the cluster manager, via some "agent" scripts, or the admin/operator, either directly, or via some other scripts. DRBD does never go Primary by itself. And that is all in the User's Guide ;-) -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com