From: Suresh Babu Kandukuru <suresh.babu.kandukuru@oracle.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: bmr@redhat.com
Subject: Re: Device mapper target driver for Write tracking or Write split
Date: Mon, 12 Jan 2015 02:04:04 -0800 (PST) [thread overview]
Message-ID: <fe1cdf55-ce8a-4914-aeba-699cd928a969@default> (raw)
In-Reply-To: <20150109165924.GB17009@localhost.localdomain>
Thanks Bryn.
>>Aside from mentioning CDP and replicating data to another appliance you
>>haven't really stated what you're trying to do.
[Suresh] - > Bascilly I would like tap/track the all writes happening that mapped lun on the host ( take it as any block device on the host ) , in the format of Offset, Length and Data . and then send this data to CDP appliace . This CDP appliance has the target lun which is intially synced to source lun on the host . after receving the writes happening on host , this cdp applicance apply writes to target lun . so both source lun and target luns are in sync all the time . Can you advise me anything better now ?. Thanks again
-----Original Message-----
From: Bryn M. Reeves [mailto:bmr@redhat.com]
Sent: Friday, January 09, 2015 10:29 PM
To: device-mapper development
Cc: vgoyal@redhat.com
Subject: Re: [dm-devel] Device mapper target driver for Write tracking or Write split
On Fri, Jan 09, 2015 at 07:51:08AM -0800, Suresh Babu Kandukuru wrote:
> Bryn, Thanks for quick reply. Below items helps to do mirroring and replication . I am looking for something which can track writes( device mapper based block level filter driver) as explained in the below diagram in Linux open source community .
Anything that's doing mirroring or replication (or many other useful
target functions) is going to need to 'track' writes (normally by
copying them and keeping track of the copies in the target).
The device-mapper core provides infrastructure to help with this but if
none of the existing dm targets provide the functionality you need then
you will either need to create one from scratch or extend whatever
current target best matches your needs.
Aside from mentioning CDP and replicating data to another appliance you
haven't really stated what you're trying to do.
Regards,
Bryn.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2015-01-12 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 5:23 Device mapper target driver for Write tracking or Write split Suresh Babu Kandukuru
2015-01-09 14:23 ` Vivek Goyal
2015-01-09 14:51 ` Suresh Babu Kandukuru
2015-01-09 15:13 ` Bryn M. Reeves
2015-01-09 15:51 ` Suresh Babu Kandukuru
2015-01-09 16:59 ` Bryn M. Reeves
2015-01-12 10:04 ` Suresh Babu Kandukuru [this message]
2015-01-12 9:34 ` Zdenek Kabelac
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=fe1cdf55-ce8a-4914-aeba-699cd928a969@default \
--to=suresh.babu.kandukuru@oracle.com \
--cc=bmr@redhat.com \
--cc=dm-devel@redhat.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 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.