From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Use fast device only for metadata?
Date: Mon, 8 Feb 2016 22:12:42 +0000 (UTC) [thread overview]
Message-ID: <pan$dd516$c0f5f933$630bef62$f9ac950d@cox.net> (raw)
In-Reply-To: 87twliri6m.fsf@thinkpad.rath.org
Nikolaus Rath posted on Mon, 08 Feb 2016 13:44:17 -0800 as excerpted:
> Otherwise I'll give bcache a shot. I've avoided it so far because of the
> need to reformat and because of rumours that it doesn't work well with
> LVM or BTRFS. But it sounds as if that's not the case..
Bcache used to have problems with btrfs, but as I and others have
mentioned, we have people known to be using btrfs with bcache on the
list, and it has been working fine for quite some time, now.
Bcache vs. LVM, OTOH, I know nothing about. Tho to be fair I guess I'm a
bit anti-LVM biased myself, as it seems a bit too much complexity for the
offered advantages, and when I tried it some time ago along with mdraid,
I decided to keep the mdraid, but kill the lvm as too complex to be
confident I could manage it correctly under the pressures of a disaster
recovery situation, possibly with limited access to documentation,
manpages, other recovery tools, etc. MDRaid, OTOH, was easier to
administer, in part because it's possible to assemble mdraid direct from
the kernel without userspace (initr* or the like if / is on it), and I
successfully managed it thru various issues over some time.
Of course these days I use multi-device btrfs directly, no mdraid, and a
multi-device btrfs root unfortunately does seem to require an initr*, but
its other advantages outweigh the additional complexity of having to use
an initr*, so...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-02-08 22:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 19:06 Use fast device only for metadata? Nikolaus Rath
2016-02-07 20:07 ` Kai Krakow
2016-02-07 20:59 ` Martin Steigerwald
2016-02-08 1:04 ` Duncan
2016-02-08 12:24 ` Austin S. Hemmelgarn
2016-02-08 13:20 ` Qu Wenruo
2016-02-08 13:29 ` Austin S. Hemmelgarn
2016-02-08 14:23 ` Qu Wenruo
2016-02-08 21:44 ` Nikolaus Rath
2016-02-08 22:12 ` Duncan [this message]
2016-02-09 7:29 ` Kai Krakow
2016-02-09 16:09 ` Nikolaus Rath
2016-02-09 21:43 ` Kai Krakow
2016-02-09 22:02 ` Chris Murphy
2016-02-09 22:38 ` Nikolaus Rath
2016-02-10 1:12 ` Henk Slager
2016-02-09 16:10 ` Nikolaus Rath
2016-02-09 21:29 ` Kai Krakow
2016-02-09 18:23 ` Henk Slager
2016-02-09 13:22 ` Austin S. Hemmelgarn
2016-02-10 4:08 ` Nikolaus Rath
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='pan$dd516$c0f5f933$630bef62$f9ac950d@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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.