From: Karen Shaeffer <shaeffer@neuralscape.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot support for LVM2?
Date: Tue, 18 May 2004 10:24:18 -0700 [thread overview]
Message-ID: <20040518172418.GA23849@synapse.neuralscape.com> (raw)
In-Reply-To: <20040517133351.L5945@homer.msp.redhat.com>
On Mon, May 17, 2004 at 01:33:51PM -0500, Alasdair G Kergon wrote:
> On Mon, May 17, 2004 at 01:36:21PM -0400, Vinesh Christopher wrote:
> > When is the official stable release of
> > Snapshot support for LVM2?
>
> Starting from http://sources.redhat.com/dm,
>
> Stable 2.4.26 kernel patch is in:
> ftp://sources.redhat.com/pub/dm/device-mapper.1.00.17.tgz
>
> For 2.6, there is not a stable snapshot release yet, but it's close.
> The snapshot support in
> ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.6-rc2/2.6.6-rc2-udm1.tar.bz2
> is the best available; there's still an issue with SMP.
>
> Alasdair
Hi Alasdair,
I was hoping you folks would at least rev the 2.6-unstable patchset for the
2.6.6 kernel that was recently released. Most of the 2.6.6-rc2-udm1 patchset
is included in 2.6.6. The 2.6.6-rc3 patchset is not included in the
2.6.6-rc2-udm1 patchset.
Evms has already been updated for the 2.6.6 release of the kernel. Can you
please advise me when the LVM2 snapshot patchset will be updated for this
latest released kernel version?
Will someone explain to me the pros and cons between using LVM2 and evms?
Thanks,
Karen
--
Karen Shaeffer
Neuralscape, Palo Alto, Ca. 94306
shaeffer@neuralscape.com http://www.neuralscape.com
next prev parent reply other threads:[~2004-05-18 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 17:36 [linux-lvm] Snapshot support for LVM2? Vinesh Christopher
2004-05-17 18:33 ` Alasdair G Kergon
2004-05-18 17:24 ` Karen Shaeffer [this message]
2004-05-20 16:24 ` Alasdair G Kergon
2004-05-22 5:01 ` Craig Ringer
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=20040518172418.GA23849@synapse.neuralscape.com \
--to=shaeffer@neuralscape.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