From: arnaud gaboury <arnaud.gaboury@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Bcache on btrfs: the perfect setup or the perfect storm?
Date: Wed, 8 Apr 2015 08:59:52 +0200 [thread overview]
Message-ID: <CAK1hC9v9ADdguR+frFPix02U2u-+fuJgaV-cJi0F55fOfeECtg@mail.gmail.com> (raw)
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?
Thank you
--
google.com/+arnaudgabourygabx
next reply other threads:[~2015-04-08 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 6:59 arnaud gaboury [this message]
2015-04-08 19:02 ` Bcache on btrfs: the perfect setup or the perfect storm? Kai Krakow
[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=CAK1hC9v9ADdguR+frFPix02U2u-+fuJgaV-cJi0F55fOfeECtg@mail.gmail.com \
--to=arnaud.gaboury@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).