All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Zdenek Kabelac <zkabelac@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM send/receive support?
Date: Mon, 5 Jun 2017 10:48:54 +0200	[thread overview]
Message-ID: <4495a5e6-6c92-97c0-c4ba-11d8a78893da@assyoma.it> (raw)
In-Reply-To: <c9020a11-12ff-3900-6e5f-8fad09e9d91b@redhat.com>

Hi Zdenek,
thanks for pointing me to thin_delta - very useful utility. Maybe I can 
code around it...

As an additional question, is direct lvm2 support for send/receive 
planned, or not?

Thanks.

On 05/06/2017 10:44, Zdenek Kabelac wrote:
> Dne 5.6.2017 v 10:11 Gionatan Danti napsal(a):
>> Hi all,
>> I wonder if using LVM snapshots (even better: lvmthin snapshots, which 
>> are way faster) we can wire something like zfs or btrfs send/receive 
>> support.
>>
>> In short: take a snapshot, do a full sync, take another snapshot and 
>> sync only the changed blocks.
>>
>> I know that exists an utility called lvmsync[1], but it seem not 
>> maintained anymore. Any suggestion on how to do something similar?
> 
> 
> Hi
> 
> Unfortunately there is not yet direct lvm2 support - but you can do it 
> manually via  thin-pool and it support tools.
> 
> Look at the tool  'thin_delta'  which you can use exactly for the 
> purpose you describe.
> 
> Regards
> 
> Zdenek
> 

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2017-06-05  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  8:11 [linux-lvm] LVM send/receive support? Gionatan Danti
2017-06-05  8:44 ` Zdenek Kabelac
2017-06-05  8:48   ` Gionatan Danti [this message]
2017-06-05  9:11     ` 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=4495a5e6-6c92-97c0-c4ba-11d8a78893da@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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.