Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, Sep 28, 2007 at 07:46:55AM -0700, Kelly Byrd wrote: > I may have answered my own question. Searching the archives, > I found this from Lars: > > | why not for a clean reboot of a standalone Primary? > | > | first, because _every_ clean reboot looks the same way: > | become secondary, disconnect, unconfigure, reboot. > | so we have been "disconnected" (degraded?) before the reboot. > | > | second, because if you do a clean reboot, > | aparently you are at the box anyways, > | so you can interactively interrupt the "wait-forever". > > Not true. I'm ssh'd into both nodes doing administrative work. > I cleanly bring down the drbd services, do my thing, then reboot > them with 'reboot', intending the boxes to come back into service > or at least let me ssh in after they reboot. I'm not physically > at the box. well. not physically, right. but mentally, ok. and since it is a remote box, the first thing that should come up is the sshd. if you configured ssh to come up last, well, you have some homework to do :) (and, there are serial consoles, and remote access processors, too.) so, yes, you are able to ssh in after they reboot, and fix it, if there is something to fix. -- : Lars Ellenberg http://www.linbit.com : : DRBD/HA support and consulting sales at linbit.com : : LINBIT Information Technologies GmbH Tel +43-1-8178292-0 : : Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 : __ please use the "List-Reply" function of your email client.