From: "Davis, Matthew" <Matthew.Davis.2@team.telstra.com>
To: Zdenek Kabelac <zkabelac@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] how to copy a snapshot, or restore snapshot without deleting it
Date: Tue, 15 Jan 2019 23:03:21 +0000 [thread overview]
Message-ID: <SYBPR01MB3931031A54431A1F999F31B4C2810@SYBPR01MB3931.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <691ff9d7-78c3-b36d-7153-b54c589bb12f@redhat.com>
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
[lvol0_pmspare] centos ewi------- 760.00m
pool00 centos twi-aotz-- <1.46t 0.18 3.14
[pool00_tdata] centos Twi-ao---- <1.46t
[pool00_tmeta] centos ewi-ao---- 760.00m
root centos Vwi-aotz-- <1.46t pool00 0.16
swap centos -wi-ao---- 4.00g
v01 centos Vwi---tz-k <1.46t pool00 root
```
Regards,
Matt
-----Original Message-----
From: Zdenek Kabelac [mailto:zkabelac@redhat.com]
Sent: Tuesday, 15 January 2019 9:50 PM
To: LVM general discussion and development <linux-lvm@redhat.com>; Davis, Matthew <Matthew.Davis.2@team.telstra.com>; Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: how to copy a snapshot, or restore snapshot without deleting it
Dne 14. 01. 19 v 23:44 Davis, Matthew napsal(a):
> Hi Zdenek,
>
> `sudo lvs --version` says :
>
> LVM version: 2.02.180(2)-RHEL7 (2018-07-20)
> Library version: 1.02.149-RHEL7 (2018-07-20)
> Driver version: 4.37.1
>
> So that means it's version 2, right?
>
> (I'm running the latest version of CentOS.)
Hmm - version looks fine
>> $sudo lvconvert --merge centos/mySnap1
>> centos/mySnap1 is not a mergeable logical volume
>>
>
> Hi
>
> Aren't you using some quite ancient version of lvm2 ?
> You need to use lvm2 which does support thin volume merging
>
Can you paste 'lvs -a' prior this operation ?
If the lvm2 tells you that 'mySnap1' is not mergable LV - then it likely has no 'origin' to merge into.
Zdenek
next prev parent reply other threads:[~2019-01-15 23:03 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 [this message]
2019-01-16 13:55 ` Zdenek Kabelac
2019-01-17 1:12 ` Davis, Matthew
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:
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=SYBPR01MB3931031A54431A1F999F31B4C2810@SYBPR01MB3931.ausprd01.prod.outlook.com \
--to=matthew.davis.2@team.telstra.com \
--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 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).