public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Re: caching device setup
Date: Wed, 08 Apr 2015 20:56:41 +0200	[thread overview]
Message-ID: <98agvb-l7r.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: 498317a297a1038028f1393da9b49231@de.mcbf.net

David Mohr <david@mcbf.net> schrieb:

> On 2015-04-06 09:44, arnaud gaboury wrote:
>> Here is my overall plan:
>> 
>> root filesystem & OS on a SSD
>> DB and other stuff on HD.
>> Use ssd as caching device and HD as backing.
>> 
>> Shall I partition the SSD with : one partition for OS and one empty
>> for bcache? Or install the OS on the whole SSD and use the whole SSD
>> as caching device?
>> 
>> Thank you for hint.
> 
> So this is just depending on your preference, how big the SSD is, and
> how much space you expect your OS to take up.
> 
> Personally I split my SSD into two partitions: one for the root FS, and
> the other as a caching device for /home.

The other preference is valid, too: I chose to put bcache only on the SSD to 
get maximum benefit from its capacity, rootfs and home dynamically share the 
cache then depending on demands. So rootfs is a bit slower as natively on 
SSD but home can gain much more because unsed parts of the rootfs are 
available for caching.

The split-setup preference in turn gives you a fallback boot option in case 
bcache chokes: You still have a working rootfs to do repairs or restore 
backups. In my setup I encounter that problem with a working USB3-HD mirror 
of my system I can boot and restore from which is synced and snapshotted 
every night (so it also protects against accidental file deletion synced 
undetected into the backup). Most valuable data is stored remotely (photos, 
source code, documents, configuration, etc).

-- 
Replies to list only preferred.

  reply	other threads:[~2015-04-08 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 15:44 caching device setup arnaud gaboury
2015-04-06 15:57 ` David Mohr
2015-04-08 18:56   ` Kai Krakow [this message]
2015-04-09  3:05     ` Lidong Zhong
2015-04-10 22:26       ` Kai Krakow
2015-04-13  7:58         ` Lidong Zhong
2015-04-09  3:08     ` Lidong Zhong
     [not found] ` <CAPBO7TY13PYVh3d0bt3tkc_+_vJVybCy-kBBT223VfPmQkjuWw@mail.gmail.com>
2015-04-06 17:44   ` arnaud gaboury

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=98agvb-l7r.ln1@hurikhan77.spdns.de \
    --to=hurikhan77@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox