All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongsu Park <dongsu.park-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Heiko Wundram <modelnine-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache hangs with continuous write I/O to SSD device, bcache device stops working
Date: Fri, 22 Mar 2013 15:16:13 +0100	[thread overview]
Message-ID: <20130322141613.GA29496@gmail.com> (raw)
In-Reply-To: <514C4FC1.6090804-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>

On 22.03.2013 13:34, Heiko Wundram wrote:
> Hey!
> 
> I've checked out multiple trunks over the last two weeks of the
> current bcache repository (all 3.8.0+), and they all exhibit the
> same kind of broken behaviour: after some time (generally around 6
> hours), I/O to the bcache device stops working (I have layered LVM
> on top of it, and those devices also stop working, naturally), and
> the SSD that's part of the cache set spins continuously at around
> 50MB/s I/O on write. It is irrelevant whether I enable discard or
> not. I've only tested this with writeback mode.

Hi Heiko,

that sounds pretty much the same as what I experienced this week.
After finishing some write benchmarks on a bcache device, dirty data
blocks have to be synchronized to backing devices really slowly.
(20~30 MB/s in my case)
That sync job usually takes more than 5 minutes,
which makes end users unable to do anything.

My test environment:
kernel 3.4.23 with bcache patches backported from master.
Backing device is configured as MD-RAID10 on spindle drives.
Cache mode is writeback.

I've also tested with bcache-3.2,
but it was not much different from 3.4+.

Regards,
Dongsu

> 
> Is this a known problem?
> 
> -- 
> --- Heiko.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-03-22 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 12:34 bcache hangs with continuous write I/O to SSD device, bcache device stops working Heiko Wundram
     [not found] ` <514C4FC1.6090804-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>
2013-03-22 14:16   ` Dongsu Park [this message]
     [not found]     ` <20130322141613.GA29496-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-22 14:19       ` Heiko Wundram
     [not found]         ` <514C687C.4010304-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>
2013-03-27 19:17           ` Heiko Wundram

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=20130322141613.GA29496@gmail.com \
    --to=dongsu.park-eikl63zcoxah+58jc4qpia@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=modelnine-EqIAFqbRPK3NLxjTenLetw@public.gmane.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.