[linux-lvm] snapshot looses origin when other snapshot is merged to the same origin

Chris Murphy lists at colorremedies.com
Fri Sep 28 16:59:55 UTC 2018

On Fri, Sep 28, 2018 at 6:57 AM, Zbigniew Kostrzewa
<kostrzewa at 9livesdata.com> wrote:
> Hi,
> I have a question related to multiple snapshots of the same thin volume. My
> scenario is that I create a thin pool, a thin volume and two snapshots of
> that thin volume. Both snapshots have the thin volume set as the origin
> volume. However, after I merge one of the snapshots to the origin then the
> second snapshot looses information about the origin.
> The question is if that is an expected behavior or if I am doing something
> wrong? Is there a way to make the second snapshot keep having the origin
> with merged first snapshot as its origin?

What file system are you using? And what lvm commands are you using
for all of this?

Someone else will have to answer the merging question, as it's not
something I've ever used or expect to use with thin volumes. Merging,
to me, sounds like a thick volume snapshots convention.

With thin volumes, each snapshot, even though it initially points to
an origin, is it's own completely independent volume. Given a thin
volume A, and snapshots created with 'lvcreate -s vg/A -n B' and
'lvcreate -s vg/A -n C' my experience is that A B C are initially
identical, and modifying A does not change B or C. Modifying B does
not change A or C. Modifying C does not change A or B.

By default, thin volume snapshots are not active volumes. So they're
not mountable. And once two or more are active, there's the potential
for confusion because you have literally two file systems that are
identical as far as the kernel is concerned. They have identical
volume UUIDs. I know XFS will refuse to mount a 2nd volume with the
same UUID as an already mounted file system; and while this can be
inhibited at mount time, I do not know the consequences.

Chris Murphy

More information about the linux-lvm mailing list