From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] drbd.ocf: drbdsetup v9 has no sh-status command
Date: Mon, 11 Jul 2016 18:27:34 +0200 [thread overview]
Message-ID: <20160711162734.GC13335@soda.linbit> (raw)
In-Reply-To: <B7D370631C221640AE09F705C57A14F3732A0E50@W2K050.campus.gsi.de>
On Fri, Jul 08, 2016 at 11:26:52AM +0000, Miedzik, Piotr Bogdan wrote:
> I've found mistake in drbd.ocf in line 1045 anyway.
> Kernel module version should be checked in opposite order.
That's not the only thing missing wrt drbd 9 and pacemaker integration.
I have some unfinished work around, which eventually will find its way
into the repositories and packages "soon".
But for now, it's unfinished :-|
--
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support
DRBD® and LINBIT® are registered trademarks of LINBIT
next prev parent reply other threads:[~2016-07-11 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:58 [Drbd-dev] [PATCH] drbd.ocf: drbdsetup v9 has no sh-status command Miedzik, Piotr Bogdan
2016-07-08 11:26 ` Miedzik, Piotr Bogdan
2016-07-11 16:27 ` Lars Ellenberg [this message]
2016-07-12 8:53 ` Miedzik, Piotr Bogdan
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=20160711162734.GC13335@soda.linbit \
--to=lars.ellenberg@linbit.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