From: Wei Liu <wei.liu2@citrix.com>
To: Shriram Rajagopalan <rshriram@gmail.com>
Cc: imhy.yang@gmail.com, Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Remus and blktap2
Date: Fri, 22 Apr 2016 19:14:45 +0100 [thread overview]
Message-ID: <20160422181445.GC13015@citrix.com> (raw)
In-Reply-To: <CAP8mzPPy4pAOyH6stOXkRD+0nqhAbSO2a_7gtLb2ArFuqnN9qw@mail.gmail.com>
On Fri, Apr 22, 2016 at 06:07:46PM +0000, Shriram Rajagopalan wrote:
> Blktap2 was the first disk backend implementation. I moved Remus to DRBD
> because it had disk resynchronization support. For eg, when primary fails,
> backup takes over. When primary comes back online, DRBD would automatically
> resynchronize new changes from the backup disk to the primary disk and will
> continue to keep them synchronized.
> At this stage, you have the option of starting Remus replication from
> backup to primary, or, migrating the VM back to the primary host and doing
> the primary to backup replication.
>
> The DRBD support (last I remember) is quite out of date, because the Remus
> DRBD kernel module I wrote relies on an older kernel version (3.4?) and
> older DRBD code base (8.1 I think).
>
I should have given more context. We may want to remove blktap2 from
xen.git in the future. Will that break remus?
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-22 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 16:15 Remus and blktap2 Wei Liu
2016-04-22 18:07 ` Shriram Rajagopalan
2016-04-22 18:14 ` Wei Liu [this message]
2016-04-22 18:20 ` Shriram Rajagopalan
2016-04-22 18:24 ` Wei Liu
2016-04-23 11:35 ` Pasi Kärkkäinen
2016-04-23 14:02 ` Shriram Rajagopalan
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=20160422181445.GC13015@citrix.com \
--to=wei.liu2@citrix.com \
--cc=imhy.yang@gmail.com \
--cc=rshriram@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.