public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Anderson <rosander@dsotm.net>
To: Peter Kieser <peter@kieser.ca>, Francis Moreau <francis.moro@gmail.com>
Cc: kmo@daterainc.com, linux-bcache@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH] bcache: fix uninterruptible sleep in writeback thread
Date: Thu, 15 May 2014 12:29:53 -0500	[thread overview]
Message-ID: <5374F991.8090802@dsotm.net> (raw)
In-Reply-To: <5374E8DB.5050705@kieser.ca>

On 5/15/2014 11:18 AM, Peter Kieser wrote:
>
> On 2014-05-15 1:02 AM, Francis Moreau wrote:
>> Eventually I would suggest to mark bcache as an experimental thing since
>> it's really not ready for production, just take a look at the bcache
>> mailing list to see why. At least people won't be disappointed when
>> they'll use bcache and see ton of koops.
>
> I'm going to second this request to mark bcache as experimental. XFS 
> performance has been stunted (almost DoS condition) since 3.10.4, 
> btrfs doesn't currently work and Kent is leaving it up to the btrfs 
> team to fix the bugs in either bcache or btrfs. Multiple 
> deadlocks/interruptible sleeps and corruption.
>
> -Peter
>
Greetings,

     First let me say I can empathize with your struggles and agree 
these bugs do need to be resolved. There's been a lot of work going into 
resolving the issues without avail. Sometimes the bugs are other teams 
issues as they are not following system that is outlined.
      I'd like to represent the other side of the coin here. I'm aware 
of numerous storage solution situations where bcache has been stable and 
in production for 18-24 months. I myself have over 20 systems in place 
with numerous file systems running without issues. There are storage 
vendors in the process of introducing into their next release. If it all 
possible, lets try to reach out to other developers and help Kent with 
getting these few issues tracked down. They are obviously tricky. Again 
it is up to others to decide.

Thanks,
Ross Anderson

  reply	other threads:[~2014-05-15 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 21:52 [PATCH] bcache: fix uninterruptible sleep in writeback thread Slava Pestov
2014-05-02  7:20 ` Daniel Smedegaard Buus
2014-05-02  8:10   ` Daniel Smedegaard Buus
2014-05-05 22:30 ` Nikolay Amiantov
2014-05-12 18:27   ` Peter Kieser
2014-05-15  8:02     ` Francis Moreau
2014-05-15 16:18       ` Peter Kieser
2014-05-15 17:29         ` Ross Anderson [this message]
2014-05-15 17:30       ` Jens Axboe
2014-06-02 14:07         ` Francis Moreau
2014-07-25  7:30           ` Francis Moreau
2014-09-05  7:08             ` Francis Moreau
2014-05-17  5:47 ` Pavel Goran

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=5374F991.8090802@dsotm.net \
    --to=rosander@dsotm.net \
    --cc=axboe@kernel.dk \
    --cc=francis.moro@gmail.com \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=peter@kieser.ca \
    /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