From: Ming Zhang <mingz@ele.uri.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Progress on LVM2 snapshots
Date: Fri, 29 Jul 2005 17:13:49 -0400 [thread overview]
Message-ID: <1122671629.5558.66.camel@localhost.localdomain> (raw)
In-Reply-To: <20050729204757.GP23710@agk.surrey.redhat.com>
thanks!
so when is the RHEL4 Update 3 timescale? :)
will try the patches u mentioned.
ming
On Fri, 2005-07-29 at 21:47 +0100, Alasdair G Kergon wrote:
> On Thu, Jul 28, 2005 at 01:44:00PM -0400, Ming Zhang wrote:
> > 1) very hard to solve technically. or
> > 2) not so easy but doable, just no time and human resource?
>
> The hardest part of the fix involves changing the sequence of
> device-mapper ioctls that LVM2 uses, and that's a couple of weeks'
> development work, now pencilled into the RHEL4 Update 3 timescale.
>
> In the meantime, you can apply the snapshot patches in the -udm
> tree and use 'dmsetup' manually to activate and deactivate snapshots
> when lvm2 fails.
>
> Patches 8 and 9 at:
> ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.12-rc2/2.6.12-rc2-udm1/
> (Further patches are needed, but those two plus correct dmsetup use
> should avoid machine lockups.)
>
> Alasdair
prev parent reply other threads:[~2005-07-29 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 11:45 [linux-lvm] Progress on LVM2 snapshots Mukund
2005-07-28 17:44 ` Ming Zhang
2005-07-28 20:06 ` Jonathan E Brassow
2005-07-28 20:26 ` Ming Zhang
2005-07-28 20:45 ` Jonathan E Brassow
2005-07-28 20:50 ` Ming Zhang
2005-07-29 20:47 ` Alasdair G Kergon
2005-07-29 21:13 ` Ming Zhang [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=1122671629.5558.66.camel@localhost.localdomain \
--to=mingz@ele.uri.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).