From: Iustin Pop <iustin@google.com>
To: drbd-dev@lists.linbit.com
Cc: Iustin Pop <iustin@google.com>
Subject: [Drbd-dev] [PATCH 0/3] Implement {begin|after}-resync-source handlers
Date: Mon, 17 May 2010 14:37:57 +0200 [thread overview]
Message-ID: <cover.1274099535.git.iustin@google.com> (raw)
These small patches duplicate the resync-target handlers for the other
end of the connection.
Some notes:
- I'm not familiar with drbdadm itself, so I'm not sure if the changes
to it are sane; I did check and test that the kernel changes are fine
and fire the proper callbacks, but was not able to test the drbdadm
configuration
- Aborting if the userspace helper exits with non-zero code is done to
mirror the before-resync-target helper; but ignoring its result is
another choice, if tearing down the connections is deemed to harsh
Iustin Pop (3):
Implement before|after-resync-source in drbdadm
Make the drbd driver generate resync-source callbacks
Update documentation for resync-source handlers
documentation/drbd.conf.xml | 27 ++++++++++++++++++++++++++-
drbd/drbd_worker.c | 14 ++++++++++++++
scripts/drbd.conf.example | 4 ++++
scripts/global_common.conf | 2 ++
user/drbdadm_main.c | 2 ++
user/drbdadm_scanner.fl | 2 ++
6 files changed, 50 insertions(+), 1 deletions(-)
next reply other threads:[~2010-05-17 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 12:37 Iustin Pop [this message]
2010-05-17 12:37 ` [Drbd-dev] [PATCH 1/3] Implement before|after-resync-source in drbdadm Iustin Pop
2010-05-17 12:37 ` [Drbd-dev] [PATCH 2/3] Make the drbd driver generate resync-source callbacks Iustin Pop
2010-05-17 12:38 ` [Drbd-dev] [PATCH 3/3] Update documentation for resync-source handlers Iustin Pop
2010-05-17 21:44 ` [Drbd-dev] [PATCH 0/3] Implement {begin|after}-resync-source handlers Philipp Reisner
2010-05-18 8:52 ` Iustin Pop
2010-05-18 12:05 ` Philipp Reisner
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=cover.1274099535.git.iustin@google.com \
--to=iustin@google.com \
--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