From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
"Davis, Matthew" <Matthew.Davis.2@team.telstra.com>
Subject: Re: [linux-lvm] how to copy a snapshot, or restore snapshot without deleting it
Date: Mon, 21 Jan 2019 11:32:29 +0100 [thread overview]
Message-ID: <17262222-82a9-e5cc-5c2c-13e11d424644@redhat.com> (raw)
In-Reply-To: <SYBPR01MB393109FBE5C800688A72F90BC29C0@SYBPR01MB3931.ausprd01.prod.outlook.com>
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.
>
Hi
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.
Zdenek
next prev parent reply other threads:[~2019-01-21 10:32 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 [this message]
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=17262222-82a9-e5cc-5c2c-13e11d424644@redhat.com \
--to=zkabelac@redhat.com \
--cc=Matthew.Davis.2@team.telstra.com \
--cc=linux-lvm@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).