From: Mike Snitzer <snitzer@redhat.com>
To: Brassow Jonathan <jbrassow@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
data <data@cogolabs.com>, Elvin Cako <ecako@cogolabs.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Setting up LVM cache causes crash
Date: Thu, 30 Oct 2014 18:45:36 -0400 [thread overview]
Message-ID: <20141030224536.GC654@redhat.com> (raw)
In-Reply-To: <45156BF3-4E7B-4F7B-82A5-187FC5970D4D@redhat.com>
On Thu, Oct 30 2014 at 12:41pm -0400,
Brassow Jonathan <jbrassow@redhat.com> wrote:
> Elvin,
>
> One of the bugs I referenced earlier has been fixed upstream. You may need to grab the latest upstream LVM and kernel sources. If you are waiting to see this fixed in a distribution, the earliest is likely to be rhel7.1 (followed by rhel6.7).
>
> If you continue to have issues like this, please contact the dm-devel mailing list (CC’ed on this mail).
We actually would rather a RHEL bug get a proper redhat bugzilla, but
yes, this issue that Elvin reported against RHEL7 appears identical to
this BZ: https://bugzilla.redhat.com/1080894
I have no initial reason to believe this issue is RHEL-only (meaning it
likely exists upstream too). I've gone ahead and made the bug public now.
prev parent reply other threads:[~2014-10-30 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 16:45 [linux-lvm] Setting up LVM cache causes crash Elvin Cako
2014-09-02 22:00 ` Brassow Jonathan
2014-09-03 15:58 ` [linux-lvm] [data] " Elvin Cako
2014-09-03 16:29 ` Elvin Cako
2014-09-08 15:58 ` Brassow Jonathan
2014-09-08 16:03 ` Brassow Jonathan
2014-09-17 15:59 ` Elvin Cako
2014-09-24 4:45 ` Brassow Jonathan
2014-09-25 21:05 ` Elvin Cako
2014-10-16 18:31 ` Elvin Cako
2014-10-30 16:41 ` [linux-lvm] [data] " Brassow Jonathan
2014-10-30 22:45 ` 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=20141030224536.GC654@redhat.com \
--to=snitzer@redhat.com \
--cc=data@cogolabs.com \
--cc=dm-devel@redhat.com \
--cc=ecako@cogolabs.com \
--cc=jbrassow@redhat.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).