linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Re: Bcache on btrfs: the perfect setup or the perfect storm?
Date: Wed, 08 Apr 2015 21:02:08 +0200	[thread overview]
Message-ID: <hiagvb-l7r.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: CAK1hC9v9ADdguR+frFPix02U2u-+fuJgaV-cJi0F55fOfeECtg@mail.gmail.com

arnaud gaboury <arnaud.gaboury@gmail.com> schrieb:

> I plan to setup Bcache on  Btrfs SSD/HD caching/backing device. The
> box will be a server, but not a production one.
> 
> I know this scheme is not recommended and can be a cause of filesystem
> corruption. But as I like living on the edge, I want to give a try,
> with a tight backup policy.
> 
> Any advice? Any settings that could be worth to avoid future drama?

See my recommendations about partitioning here I just posted:
http://permalink.gmane.org/gmane.linux.kernel.bcache.devel/2865

Take care of the warnings about trimming/enabling discard. I'd at least test 
it if you want to use it before trusting your kitty to it. ;-)

BTW: I'm planning on a similar system tho the plans may well be 1 or 2 years 
in the future and the system is planned to be based off bcache/btrfs. It 
should become a production container-VM host. We'll see. Fallback plan is to 
use a battery-backed RAID controller with CacheCade (SSDs as volume cache).

-- 
Replies to list only preferred.

  reply	other threads:[~2015-04-08 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  6:59 Bcache on btrfs: the perfect setup or the perfect storm? arnaud gaboury
2015-04-08 19:02 ` Kai Krakow [this message]
     [not found] ` <55257b31.0308c20a.75a0.7849@mx.google.com>
2015-04-10 14:42   ` arnaud gaboury
2015-04-10 23:33     ` Kai Krakow
2015-04-10 23:49       ` Kai Krakow

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=hiagvb-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;
as well as URLs for NNTP newsgroup(s).