From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] multiple levels of snapshots
Date: Mon, 23 Apr 2007 19:58:03 +0100 [thread overview]
Message-ID: <20070423185803.GM26983@agk.fab.redhat.com> (raw)
In-Reply-To: <fd8dc0d20704231154l4a512d7ag2df2405ebcb17cd2@mail.gmail.com>
On Mon, Apr 23, 2007 at 02:54:37PM -0400, Boris Ostrovsky wrote:
> From what I can see, LVM tools don't allow creating multiple levels of
> snapshots (i.e. creating a
> snapshot of a snapshot). Is this a fundamental property of LVM/device
> mapper architecture
> or is it that this feature simply hasn't made it to LVM (yet)?
You could indeed set it up outside LVM using dmsetup.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2007-04-23 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 18:54 [linux-lvm] multiple levels of snapshots Boris Ostrovsky
2007-04-23 18:58 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-26 14:00 Boris Ostrovsky
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=20070423185803.GM26983@agk.fab.redhat.com \
--to=agk@redhat.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).