[DRBD-user] drbdadm adjust

Lars Ellenberg lars.ellenberg at linbit.com
Fri Apr 11 17:08:53 CEST 2008

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, Apr 11, 2008 at 07:52:15AM -0600, Damon Estep wrote:
> 
> 
> > -----Original Message-----
> > From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-
> > bounces at lists.linbit.com] On Behalf Of Lars Ellenberg
> > Sent: Friday, April 11, 2008 12:58 AM
> > To: drbd-user at lists.linbit.com
> > Subject: Re: [DRBD-user] drbdadm adjust
> > 
> > On Thu, Apr 10, 2008 at 10:58:43PM -0600, Damon Estep wrote:
> > >
> > >    I was under the impression that `drbdadm adjust [resource]' could
> > be
> > >    run on the node that is secondary (0.7.25), but I am finding that
> > not
> > >    to work.
> > >
> > >
> > >    I have changed the io error handler from pass_on to panic in the
> > >    resource section of drbd.conf and would like the change to take
> > >    effect, what needs to be done to get the change in place?
> > 
> > the "adjust" in 0.7 sometimes just misses some parts of the changes.
> > due to an arguably bad design decission on our part, the "on-io-error"
> > can only be changed by a new attach. that does only work if you detach
> > first. which will happen automatically in drbd 8.0 (and would catch
> you
> > a full sync, if you do it on a Primary; we need to improve on that,
> > so it won't happen "accidentally").
> > 
> > the best way for you is probably to
> > A# drbdadm down XY
> > A# drbdadm up XY
> > wait for short resync
> > switch-over
> > B# drbdadm down XY
> > B# drbdadm up XY
> > 
> > --
> > : 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 :
> [Damon Estep] 
> 
> Is there any risk making this change on one node (the current
> secondary), and then not changing the current primary to secondary and
> making the change on it for a couple of days when a maintenance window
> exists?

I think that is a reasonable approach.

> Would there be any issues if a failure occurred on the current
> primary while the two nodes had different configurations?

it would just "pass on" as it is configured now.
you'd probably need to trigger a full sync somewhen after such an event.

-- 
: 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 don't Cc me, but send to list -- I'm subscribed



More information about the drbd-user mailing list