From: "Davis, Matthew" <Matthew.Davis.email@example.com>
To: Zdenek Kabelac <firstname.lastname@example.org>,
LVM general discussion and development <email@example.com>
Subject: Re: [linux-lvm] how to copy a snapshot, or restore snapshot without deleting it
Date: Wed, 30 Jan 2019 23:58:45 +0000 [thread overview]
Message-ID: <SYBPR01MB3931BC8B19167921717F8D35C2900@SYBPR01MB3931.ausprd01.prod.outlook.com> (raw)
Yes that is exactly the option which I would love to have.
From: Zdenek Kabelac [mailto:firstname.lastname@example.org]
Sent: Monday, 28 January 2019 10:50 PM
To: LVM general discussion and development <email@example.com>; Zdenek Kabelac <firstname.lastname@example.org>; Davis, Matthew <Matthew.Davis.email@example.com>
Subject: Re: how to copy a snapshot, or restore snapshot without deleting it
Dne 21. 01. 19 v 11:32 Zdenek Kabelac napsal(a):
> Dne 18. 01. 19 v 1:53 Davis, Matthew napsal(a):
>> Hi Zdenek,
>> I assumed that LVM thin snapshots would work like git branches.
>> Since git also uses diffs on the backend, and git is popular with
>> developers, the same kind of behaviour seems reasonable to me.
> There is very good reason why the git is not really a good tool for
> storing binary data...
> Your use-case is 'very specific' sub-case of many different usability
> scenarios you can do with lvm2 -ï¿½ so while you might see some
> potential benefit if the lvm2 would work more closely to git logic, it
> would look terrible in many other situations.
Adding some more thoughts here - we can probably give user an option to control this - particularly in this case - how about something like:
lvconvert --mergesnapshot --keeporigin y|n
so if user would specify 'y' - lvm2 would relink/preserve merged snapshot as an origin for all other existing snapshots of the old origin - this would make more obvious what is going to happen when you start creating and merging lots of them into a single origin.
(yeah - maybe there could be better fitting option name - so it's more about idea here for now)
next prev parent reply other threads:[~2019-01-30 23:58 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
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 [this message]
2019-01-10 14:34 ` Tomas Dalebjörk
2019-01-11 19:29 ` Sarah Newman
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).