From: Kent Overstreet <kmo@daterainc.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: Is bcache dead?
Date: Thu, 30 Oct 2014 16:34:25 -0700 [thread overview]
Message-ID: <20141030233425.GA28233@kmo-pixel> (raw)
In-Reply-To: <54529797.2020004@hardwarefreak.com>
On Thu, Oct 30, 2014 at 02:55:03PM -0500, Stan Hoeppner wrote:
> On 10/30/2014 09:14 AM, Kent Overstreet wrote:
> > 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.
>
> Don't sweat it Kent. Don't get discouraged. Stay positive.
>
> I tried bcache a few weeks ago for a pretty niche application and it
> wasn't suitable for that workload for what I wanted it to do. I asked
> questions here to make it work but got no responses. Would have been a
> feather in your cap to had bcache on those systems--two 44TiB LUNs on
> the small ones, 14x 44TiB LUNs on the large one--if it could have been
> made to work with that workload. We'll probably fix it by modifying the
> app to do full stripe buffer writes. Yes, this is much more work than
> simply slapping in bcache, had it worked. I was looking for a quick fix.
>
> I know the demands from myself and others can create stress. But when
> you feel stressed by it, remember that the demand is a direct result of
> you creating something special, that people really want to use.
>
> You recognize and acknowledge the fact that you're a one man show right
> now. Your users know it too. Do what you can when you can, and do it
> right. I think most people will be more forgiving of delays than
> mistakes, or broken promises, or silence. Communication helps. If
> you're bogged down, just post a quick note the list letting everyone
> know. A quick update like that goes a long way, whereas silence breeds
> discontent among users, because they don't know what's going on.
>
> Keep your chin up. You'll get there, even if it takes longer than folks
> would like.
>
> Best regards,
>
> Stan
Thanks, I really do appreciate the kind words.
next prev parent reply other threads:[~2014-10-30 23:32 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
2014-10-30 19:55 ` Stan Hoeppner
2014-10-30 23:34 ` Kent Overstreet [this message]
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=20141030233425.GA28233@kmo-pixel \
--to=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=stan@hardwarefreak.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).