All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Vivek Dasmohapatra <vivek@collabora.co.uk>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Issue (as expected) when upgrading from 3.12 to 3.13.7
Date: Thu, 03 Apr 2014 18:18:35 +0200	[thread overview]
Message-ID: <533D89DB.2060306@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404031057430.4261@noise.cbg.collabora.co.uk>

On 04/03/2014 12:02 PM, Vivek Dasmohapatra wrote:
> On Sun, 30 Mar 2014, Francis Moreau wrote:
> 
> Hi Francis: A quick question for you if you have the time:
> How is the bcache constructed? ie which devices are in it?
> 

sure: I'm using bcache on a very basic setup: no MD or LVM involved.
/dev/sda4 (900Mo) is the backing device while /dev/sdb (120G) is the
cache device. On top of bcache0 I'm using ext4 and I'm using it as my
root device.

> I have had similar lockup problems when using partitions
> as backing, but not whole devices. That is to say:
> 
>     { ram0 : sdb1 }  often deadlocks for me (depending on the offset
>                      of the partition)
> 
>     { ram0 : sdb  }  always seems to work fine
> 
> Although in neither case am I able to tear down the device and
> flush it all to backing after heavy use: That always locks up
> for me. (Fortunately I'm making throwaway filesystems for a build
> daemon so that part I can live with).
> 

For now it doesn't endup to lock up (cross fingers). It only fills the
kernel logs, well I hope.

Thanks.

  reply	other threads:[~2014-04-03 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 10:53 Issue (as expected) when upgrading from 3.12 to 3.13.7 Francis Moreau
2014-03-30 11:47 ` Sitsofe Wheeler
2014-03-30 12:08   ` Francis Moreau
2014-03-30 13:04     ` Sitsofe Wheeler
2014-03-30 13:24       ` Francis Moreau
2014-04-03  9:56   ` Francis Moreau
2014-03-31  3:20 ` Peter Kieser
2014-04-01  6:51   ` Francis Moreau
2014-04-03 10:02 ` Vivek Dasmohapatra
2014-04-03 16:18   ` Francis Moreau [this message]
2014-04-03 16:21     ` Vivek Dasmohapatra
2014-04-03 20:39       ` Sam Fulcomer

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=533D89DB.2060306@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=vivek@collabora.co.uk \
    /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.