All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Wundram <modelnine-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache hangs with continuous write I/O to SSD device, bcache device stops working
Date: Wed, 27 Mar 2013 20:17:42 +0100	[thread overview]
Message-ID: <515345D6.1060803@modelnine.org> (raw)
In-Reply-To: <514C687C.4010304-EqIAFqbRPK3NLxjTenLetw@public.gmane.org>

Am 22.03.2013 15:19, schrieb Heiko Wundram:
> In my case, the syncing was still going on after around 16 hours (I
> simply let the system run after it got locked in this state). As I've
> only got around 2GB of page cache in the corresponding system that was
> used as the test bed, most probably, the system wasn't (still) flushing
> data, but rather spinning on something else.

I'm not entirely sure what difference I made, but it seems that this 
problem has disappeared (hasn't surfaced over the last three days, 
whereas before it was a matter of hours).

I've updated the kernel to statically contain bcache and the DM/md 
infrastructure (which should be unrelated, except for being part of a 
stack of block devices). Anyway, that seems to have done the trick, in 
case anybody else is experiencing this.

-- 
--- Heiko.

      parent reply	other threads:[~2013-03-27 19:17 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
     [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 [this message]

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=515345D6.1060803@modelnine.org \
    --to=modelnine-eqiafqbrpk3nlxjtenletw@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@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.