From: Pat Sailor <psalleetsile@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: SSD caching an existing btrfs raid1
Date: Tue, 19 Sep 2017 17:30:30 +0200 [thread overview]
Message-ID: <4ed24e33-09e1-c03a-912c-9d1b2bbdc835@gmail.com> (raw)
Hello,
I have a half-filled raid1 on top of six spinning devices. Now I have
come into a spare SSD I'd like to use for caching, if possible without
having to rebuild or, failing that, without having to renounce to btrfs
and flexible reshaping.
I've been reading about the several options out there; I thought that
EnhanceIO would be the simplest bet but unfortunately I couldn't get it
to build with my recent kernel (last commits are from years ago).
Failing that, I read that lvmcache could be the way to go. However, I
can't think of a way of setting it up in which I retain the ability to
add/remove/replace drives as I can do now with pure btrfs; if I opted to
drop btrfs to go to ext4 I still would have to offline the filesystem
for downsizes. Not a frequent occurrence I hope, but now I'm used to
keep working while I reshape things in btrfs, and it's better if I can
avoid large downtimes.
Is what I want doable at all? Thanks in advance for any
suggestions/experiences to proceed.
next reply other threads:[~2017-09-19 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:30 Pat Sailor [this message]
2017-09-19 15:47 ` SSD caching an existing btrfs raid1 Austin S. Hemmelgarn
2017-09-20 1:58 ` Duncan
2017-09-20 15:51 ` Psalle
2017-09-20 20:45 ` Kai Krakow
2017-09-21 6:23 ` Paul Jones
2017-09-21 16:49 ` Psalle
2017-09-20 1:33 ` Paul Jones
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=4ed24e33-09e1-c03a-912c-9d1b2bbdc835@gmail.com \
--to=psalleetsile@gmail.com \
--cc=linux-btrfs@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).