From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Hauke Laging <mailinglisten@hauke-laging.de>
Subject: Re: "create snapshots of any block device"
Date: Tue, 22 Jan 2013 11:22:27 +0000 [thread overview]
Message-ID: <50FE7673.7080407@redhat.com> (raw)
In-Reply-To: <1766138.NkjTPulnJa@inno>
On 01/22/2013 11:12 AM, Hauke Laging wrote:
> Isn't that at least misleading? Is it really possible to create a snapshot of
> e.g. /dev/sda5 without creating an *additional* device as snapshot origin?
It's possible but as you note you have to create the dm layers for the
snapshot. This means that if a non-dm device is in use you have to shut
its users down (unmount file systems etc.), create the snapshot and then
re-mount.
I've frequently used this in the past to snapshot large zero targets to
create sparse devices for testing (before --virtualsize was added to LVM2).
With device-mapper devices this is unnecessary since the top-level
device may be suspended while the snapshot layers are inserted.
Regards,
Bryn.
prev parent reply other threads:[~2013-01-22 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 11:12 "create snapshots of any block device" Hauke Laging
2013-01-22 11:22 ` Bryn M. Reeves [this message]
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=50FE7673.7080407@redhat.com \
--to=bmr@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mailinglisten@hauke-laging.de \
/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