public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: How well does bcache cope with frequently changing cache device?
Date: Mon, 5 Sep 2016 18:27:32 -0800	[thread overview]
Message-ID: <20160906022732.2y4dubiwcfmo6dkz@kmo-pixel> (raw)
In-Reply-To: <CAFvQSYTEMFptL92JhbGgKRNEkFFLm5z5nZM1hksSSeon2bX=dA@mail.gmail.com>

On Sun, Sep 04, 2016 at 07:08:04PM +0200, Clemens Eisserer wrote:
> Hi,
> 
> I am thinking about working with a root-fs on an external disk which
> can be shared amongst different computers.
> For this use-case the internal SSD could be used as caching device,
> speeding up the access to the relativly slow external storage.
> 
> What I wonder is how well bcache can cope with changing caching
> devices? Great would be if bcache could detect when a backing decive
> was used with a different caching device in the meantime and
> automatically invalidate the old/stale caching device - but to keep
> the cache unmodified when this was not the case.
> 
> Is this use-case possible with bcache?

On its own bcache won't automatically invalidate the cached data - once a
backing device is associated with a certain cache, that backing device won't
come online until either the cache device is registered, or you detach it.

So you'll have to write your own scripts to check - "hey, is this backing device
associated with this cache device? if not, detach backing device, reformat cache
device, then attach cache device and backing device".

      reply	other threads:[~2016-09-06  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 17:08 How well does bcache cope with frequently changing cache device? Clemens Eisserer
2016-09-06  2:27 ` Kent Overstreet [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=20160906022732.2y4dubiwcfmo6dkz@kmo-pixel \
    --to=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linuxhippy@gmail.com \
    /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