public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Kieser <peter@kieser.ca>
To: 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 09:18:35 -0700	[thread overview]
Message-ID: <5374E8DB.5050705@kieser.ca> (raw)
In-Reply-To: <53747499.3070000@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]


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


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]

  reply	other threads:[~2014-05-15 16:18 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 [this message]
2014-05-15 17:29         ` Ross Anderson
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=5374E8DB.5050705@kieser.ca \
    --to=peter@kieser.ca \
    --cc=axboe@kernel.dk \
    --cc=francis.moro@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox