From: markw@mohawksoft.com
To: linux-lvm@redhat.com
Subject: [linux-lvm] Snapshots of snapshots are not supported yet
Date: Mon, 8 Jul 2013 12:05:48 -0400 [thread overview]
Message-ID: <731d217f00b6d8f6c16a75cbe167baed.squirrel@mail.mohawksoft.com> (raw)
I'm trying to get a snapshot of a snapshot. I know the new thin
provisioning stuff supports this, but I'm not sure the release state is
something I can use at a customer.
Using LVM2, the snapshot format is tried and true, but inefficient if you
want to take multiple snapshots.
Looking at dmsetup, there doesn't seem like there would be an issue taking
a snapshot of a snapshot, but it is disabled in the tools.
I guess my question is this: Can it be done? Is there any reason why it
should not work?
next reply other threads:[~2013-07-08 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 16:05 markw [this message]
2013-07-08 17:41 ` [linux-lvm] Snapshots of snapshots are not supported yet Zdenek Kabelac
2013-07-08 17:57 ` markw
2013-07-08 19:03 ` Zdenek Kabelac
2013-07-10 3:45 ` markw
2013-07-10 8:25 ` Zdenek Kabelac
2013-07-10 14:45 ` markw
2013-07-10 18:43 ` Zdenek Kabelac
2013-07-10 19:16 ` markw
2013-07-10 20:12 ` markw
2013-07-10 20:15 ` Zdenek Kabelac
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=731d217f00b6d8f6c16a75cbe167baed.squirrel@mail.mohawksoft.com \
--to=markw@mohawksoft.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).