From: Alasdair G Kergon <agk@redhat.com>
To: Kristina Clair <kclair@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dm_snapshot experimental? potential repercussions?
Date: Wed, 2 Feb 2005 17:34:33 +0000 [thread overview]
Message-ID: <20050202173433.GC14097@agk.surrey.redhat.com> (raw)
In-Reply-To: <dff3752705020208024b5992@mail.gmail.com>
On Wed, Feb 02, 2005 at 11:02:49AM -0500, Kristina Clair wrote:
> I have been told that dm_snapshot is still experimental in the 2.6.10
> kernel, and I was advised not to have more than one snapshot created
> at a time for the same logical volume.
Each snapshot is independent and keeps its own separate copy of
changes, so as you increase the number of parallel snapshots you
quickly affect performance. This has always been the case for
LVM and device-mapper snapshots. Daniel Phillips is working on a
clustered snapshot implementation which at the same time addresses
this issue, allowing parallel snapshots to share their metadata.
> Basically I am just wondering what the potential problems are with
> dm_snapshot. Is there anything particular that I should look out for?
There are numerous memory allocation issues with the current dm-snapshot
implementation: in simple terms, devices or your machine can lock up,
and your system is especially vulnerable when snapshots are manipulated
(create/activate) and when your system is under load.
We think we understand the most important problems and are gradually
fixing them, but this is not a quick process because the changes have a
significant impact on the LVM2 and EVMS code bases (complex sequences of
ioctls have to change).
Join the dm-devel mailing list if you want to monitor progress.
Alasdair
--
agk@redhat.com
prev parent reply other threads:[~2005-02-02 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 16:02 Kristina Clair
2005-02-02 17:34 ` Alasdair G Kergon [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=20050202173433.GC14097@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=kclair@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®