archive mirror
 help / color / mirror / Atom feed
From: "Davis, Matthew" <>
To: Zdenek Kabelac <>,
	LVM general discussion and development <>
Subject: Re: [linux-lvm] how to copy a snapshot, or restore snapshot without deleting it
Date: Thu, 17 Jan 2019 01:12:36 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Zdenek,

What do you mean "it's origin is already gone"?
It is a snapshot of centos/root, which still is there. (I have since modified centos/root)
So the origin is still there.

I think it's because I merged the copy of the snapshot. If I merge the original snapshot, the copy remains and it's origin changes.
That seems to work.

* make snapshot fresh1
* change contents of root
* copy fresh1 to fresh2
* merge fresh1
* reboot
* root is now restored to how it was originally
* fresh 2 now has origin root

That works.
(Although I get a daunting error message every time I create a snapshot, and sometimes I get error messages on merge, but it works most of the time.)


From: Zdenek Kabelac <>
Sent: Thursday, 17 January 2019 12:55:59 AM
To: Davis, Matthew; LVM general discussion and development
Subject: Re: how to copy a snapshot, or restore snapshot without deleting it 
Dne 16. 01. 19 v 0:03 Davis, Matthew napsal(a):
> Hi Zdenek,
> Here's what I see with `sudo lvs -a`. (My snapshots are actually called `fresh` and `fresh2` not `mySnap`)
> ```
>��� LV������������� VG���� Attr������ LSize�� Pool�� Origin Data%� Meta%� Move Log Cpy%Sync Convert
>��� fresh���������� centos Vwi---tz-k� <1.46t pool00
>��� fresh2��������� centos Vwi---tz-k� <1.46t pool00 fresh

So these both LVs are snapshots� (since they were created with� s(k)ipped 
activation - however 'fresh' LV cannot be merged anymore� as it's origin is 
already gone.

But� 'lvconvert --merge� centos/fresh2'� should work - yet you need to 
manually drop 'k' flag (via lvchange).

So to have 'working' merge - you have to see something in the 'Origin' field.
If the Origin field is already 'empty' you can't be merging such LV even when 
it was originally created as 'snapshot'.

Also note that thin snapshot merging is nothing else then a bit more 'smart' 


  reply	other threads:[~2019-01-17  1:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03  4:46 [linux-lvm] how to copy a snapshot, or restore snapshot without deleting it Davis, Matthew
2019-01-03  9:32 ` Tomas Dalebjörk
2019-01-03 14:09 ` Marian Csontos
2019-01-10  6:23   ` Davis, Matthew
2019-01-10  9:45     ` Zdenek Kabelac
2019-01-14 22:44       ` Davis, Matthew
2019-01-15 10:49         ` Zdenek Kabelac
2019-01-15 23:03           ` Davis, Matthew
2019-01-16 13:55             ` Zdenek Kabelac
2019-01-17  1:12               ` Davis, Matthew [this message]
2019-01-17  9:21                 ` Zdenek Kabelac
2019-01-18  0:53                   ` Davis, Matthew
2019-01-18  9:34                     ` Zdenek Kabelac
2019-01-21 10:32                     ` Zdenek Kabelac
2019-01-28 11:49                       ` Zdenek Kabelac
2019-01-30 23:58                         ` Davis, Matthew
2019-01-10 14:34     ` Tomas Dalebjörk
2019-01-11 19:29       ` Sarah Newman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).