From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Kent Overstreet <kmo@daterainc.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: Is bcache dead?
Date: Thu, 30 Oct 2014 15:15:38 +0100 [thread overview]
Message-ID: <5452480A.1020702@profihost.ag> (raw)
In-Reply-To: <CALJ65zm0UpNKZKZmT26Gv6+CA6ijTS60+PVoCroLA4aipo-bPg@mail.gmail.com>
Hi Kent,
nice to hear you. No problem at all. I was just wondering that there was
no single response to all the bcache_gc problems people have,
Greets,
Stefan
Am 30.10.2014 um 15:14 schrieb Kent Overstreet:
> no, I've just been severely overworked, and overstressed, to the point
> that it might be time for a change of jobs - and unfortunately, there
> still isn't anyone else who can step in. It's not fun being the single
> point of failure.
>
> Sorry for going off the radar. Might be a good time to take some time
> off and try and get some upstream work done.
>
> On Thu, Oct 30, 2014 at 5:07 AM, Stefan Priebe - Profihost AG
> <s.priebe@profihost.ag> wrote:
>> Hi,
>>
>> this might be a bit aggressive - sorry for that.
>>
>> There are a lot of people having deadlocks with bcache_gc and there's no
>> dev looking into this since month.
>>
>> Greets,
>> Stefan
next prev parent reply other threads:[~2014-10-30 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 12:07 Is bcache dead? Stefan Priebe - Profihost AG
2014-10-30 14:09 ` Vasiliy Tolstov
2014-10-30 14:14 ` Stefan Priebe - Profihost AG
2014-10-30 14:15 ` Kent Overstreet
2014-10-30 14:18 ` Stefan Priebe - Profihost AG
2014-10-30 15:58 ` Thomas Stein
2014-10-30 14:14 ` Kent Overstreet
2014-10-30 14:15 ` Stefan Priebe - Profihost AG [this message]
2014-10-30 19:55 ` Stan Hoeppner
2014-10-30 23:34 ` Kent Overstreet
2014-11-06 15:03 ` Zachary Palmer
2014-11-06 22:12 ` Rolf Fokkens
2015-01-19 18:36 ` Michael Russo
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=5452480A.1020702@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=kmo@daterainc.com \
--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.