All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kmo@daterainc.com>
To: Josep Lladonosa <jlladono@gmail.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: About physically swapping backing and cache device
Date: Tue, 7 Jan 2014 13:35:58 -0800	[thread overview]
Message-ID: <20140107213558.GK9037@kmo> (raw)
In-Reply-To: <CAPBO7TYjki0s4-cMxS1ztvO=WT-8+ScH6mfZrE+YkTLuFcBqAA@mail.gmail.com>

On Tue, Jan 07, 2014 at 09:52:50AM +0100, Josep Lladonosa wrote:
> Hello,
> 
> 
> I have been using bcache for some months. Now I am with 3.12.6 kernel
> (stable! :)
> Thanks and congratulations for the good work.
> 
> I have in the laptop this configuration:
> 
> /dev/sda7 as backing device (hard drive partition)
> /dev/sdb as cache device (SSD)
> 
> 1) I would like to physically swap sda and sdb (a matter of different
> bus speeds) in order to improve ata speed for SSD. The fact is that in
> a case of this, would I have to "reregister" anything in bcache, or it
> will run referenced to UUIDs and so?

Everything's referenced with UUIDs, so it'll all just work.

> 2) I think I would have to install GRUB into /dev/sdb (it has no
> partitions defined). Would it be safe installing GRUB in a cache
> device? Future configuration would be /dev/sda for the cache (SSD) and
> /dev/sdb for the backing device (hard drive).

Bcache doesn't touch the first 4k of the device, so if it's just grub's MBR (512
bytes) that should be fine. I would verify that grub isn't touching more than
the first 4k of the device though.

  reply	other threads:[~2014-01-07 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07  8:52 About physically swapping backing and cache device Josep Lladonosa
2014-01-07 21:35 ` Kent Overstreet [this message]
2014-01-07 23:07   ` Darrick J. Wong

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=20140107213558.GK9037@kmo \
    --to=kmo@daterainc.com \
    --cc=jlladono@gmail.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 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.