From: Jason Warr <jason@warr.net>
To: "Paul B. Henson" <henson@acm.org>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Another bcache hang
Date: Fri, 22 Nov 2013 20:38:31 -0600 [thread overview]
Message-ID: <52901527.9010309@warr.net> (raw)
In-Reply-To: <001f01cee7f1$bd65e7f0$3831b7d0$@acm.org>
On 11/22/2013 08:14 PM, Paul B. Henson wrote:
>> From: Jason Warr
>> Sent: Friday, November 22, 2013 5:03 PM
>>
>> Actually that is probably veering back on topic :)
> Well, for the list maybe, but not for the thread, which has still not seen
> any debugging/troubleshooting recommendations for the bcache hang originally
> reported.
>
>> At the moment I am using Fedora 20 Beta's version of 3.11.8. I don't
>> yet have enough time with it to say how useful/stable it is. I try to
>> stick with something that has a better chance of making it into an
>> enterprise distro as that is my main focus.
> I generally run Gentoo unless there is a proprietary commercial application
> involved, in which case we use RHEL. I can't see this being backported to
> RHEL6, but possibly it might show up in RHEL7. I guess there's no firm
> release date on that yet, but scuttlebutt has it that they will be using
> kernel 3.11 (although I don't think that's intended to be an upstream LTS
> kernel), which matches the current development fedora version...
I would say there is exactly zero hope of anything exciting coming onto
RHEL6 at this point. My hope is that bcache will at least be a "tech
preview" feature in RHEL7. With the RHEL6.5 spin just dropping I sure
hope they give us some more solid direction soon on what RHEL7 should
look like.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-23 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 13:56 Another bcache hang David H. Rhodes Clymer
2013-11-22 1:07 ` Paul B. Henson
2013-11-22 3:49 ` David H. Rhodes Clymer
2013-11-22 14:35 ` Jason Warr
2013-11-22 19:51 ` Paul B. Henson
2013-11-22 20:34 ` Jason Warr
2013-11-22 23:52 ` Paul B. Henson
2013-11-23 0:38 ` Matthew Patton
2013-11-23 0:43 ` Paul B. Henson
2013-11-23 1:02 ` Jason Warr
2013-11-23 2:14 ` Paul B. Henson
2013-11-23 2:38 ` Jason Warr [this message]
2013-11-22 19:46 ` Paul B. Henson
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=52901527.9010309@warr.net \
--to=jason@warr.net \
--cc=henson@acm.org \
--cc=linux-bcache@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.