From: Prashanth Radhakrishnan <shanth@cs.utah.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Snapshot of an LVM snapshots?
Date: Thu, 24 Aug 2006 00:54:35 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0608240026110.18183@trust.cs.utah.edu> (raw)
Hi LVM Gurus,
From what I've read around, it is not possible to take a snapshot of an
LVM snapshot. Is this something that is worked upon currently as a future
enhancement? If not, why not?
To give you a background, we're working on a periodic (xen) VM
checkpointing project, using LVM for VM disk checkpointing. As we take
several snapshots of the same volume, the write throughput reduces
drastically. I conjecture this is because, for each write to the (base)
volume, each of the snapshots' mappings is checked to decide whether to
copy the blocks to the snapshot or not.
It seems that this can be helped by:
- taking a snapshot of the latest snapshot and having the writes go to
the new snapshot
or
- making LVM use only the latest snapshot for CoW as writes go to the base
volume.
Any suggestions/pointers greatly appreaciated.
thanks,
Prashanth
reply other threads:[~2006-08-24 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.61.0608240026110.18183@trust.cs.utah.edu \
--to=shanth@cs.utah.edu \
--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).