Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Sébastien Wacquiez" <sw@enix.org>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Drbd handler interfering with drbd-setup only cmd
Date: Fri, 10 Jul 2009 16:57:36 +0200	[thread overview]
Message-ID: <4A5756E0.7070401@enix.org> (raw)

Hi,


I just upgraded my setup to drbd 8.3 (from 8.0.14) and what I used to do
with drbdsetup don't work anymore.

I'm currently using drbd to do some kind of "hot replication" on the fly
; I wrote a bunch of script  (around dmsetup) that spawn some drbdsetup
and drbdmeta, let the data sync, and spawn some other to destroy the setup.

My problem is that as I don't use any config file, so when the drbd
driver try to call "drbdadm before-resync-target", it fail.

I think it's a regression ; as it's an unusual setup, it should be ok to
have a config option that desactivate this behavior. What do you think
about it ?



Wacquiez Sébastien

PS : please cc me on reply as I'm not subscribed to this mailing list

                 reply	other threads:[~2009-07-10 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5756E0.7070401@enix.org \
    --to=sw@enix.org \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox