From: "Mike Snitzer" <snitzer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshots filling and hanging up processes
Date: Thu, 23 Mar 2006 11:29:11 -0500 [thread overview]
Message-ID: <170fa0d20603230829n50943ffcr716d480e7a4b3beb@mail.gmail.com> (raw)
In-Reply-To: <20060321192427.GO26428@agk.surrey.redhat.com>
On 3/21/06, Alasdair G Kergon <agk@redhat.com> wrote:
> On Tue, Mar 21, 2006 at 01:33:24PM -0500, Brian J. Murrell wrote:
> > later FC kernel like kernel-2.6.15-1.1833_FC4.x86_64.rpm or
> > kernel-2.6.15-1.2054_FC5.x86_64.rpm?
>
> Relevant kernel patches should be going into 2.6.17.
>
> Or download from
> http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
Have these patches gone in to the RHEL4 U3 kernel? Is RHEL4 U3's lvm
snapshot support considered "officially supported by RedHat"?
Thanks for all your hard work on lvm snapshot!
Mike
prev parent reply other threads:[~2006-03-23 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 18:33 [linux-lvm] snapshots filling and hanging up processes Brian J. Murrell
2006-03-21 19:24 ` Alasdair G Kergon
2006-03-23 16:29 ` Mike Snitzer [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=170fa0d20603230829n50943ffcr716d480e7a4b3beb@mail.gmail.com \
--to=snitzer@gmail.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;
as well as URLs for NNTP newsgroup(s).