From: Marian Csontos <mcsontos@redhat.com>
To: linux-lvm@redhat.com
Cc: news-io-dx32@spamfilter.de
Subject: Re: [linux-lvm] Question before merging snapshot
Date: Tue, 03 Sep 2013 10:17:50 +0200 [thread overview]
Message-ID: <52259B2E.6090602@redhat.com> (raw)
In-Reply-To: <l02rvj$uab$1@ger.gmane.org>
On 09/02/2013 10:21 PM, Ron Schneider wrote:
>
> Hi all,
>
> Situation:
>
> I have a volume A that contains production data.
> For an experiment I created volume a' from A using
> the snapshot function.
> I then used a' for my experiment, which went very well.
>
> Now I want to merge snapshot a' back into A. I have read that the merge
> will effectively make A to be what a' was before, then a' will
> disappear. However, all examples that I found on the net referred to
> making snapshot a' then making changes to the origin A and finally using
> --merge to revert A back to a'.
> In my case though, I used the snapshot a' for writing instead of origin
> A. I just want you to confirm that --merge will function the same way
> nevertheless, thus making the modified content of a' appear in the
> origin LV A.
> Of course I will backup everything before the merge but I'd like to save
> myself unnecessary recovery cycles so I thought I'd just ask the pros
> beforehand - just to be sure.
Hi, what's in the snapshot will become content of the origin, regardless
where the writes go.
When writing to origin, merge will revert the changes made to origin
since snapshot was taken.
When writing to snapshot, merge will promote the changes made in the
snapshot to the origin.
When writing to both, changes to origin will be reverted and changes
made in snapshot will be promoted.
-- Marian
>
prev parent reply other threads:[~2013-09-03 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 20:21 [linux-lvm] Question before merging snapshot Ron Schneider
2013-09-03 8:17 ` Marian Csontos [this message]
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=52259B2E.6090602@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=news-io-dx32@spamfilter.de \
/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;
as well as URLs for NNTP newsgroup(s).