From: Nikolaus Rath <Nikolaus@rath.org>
To: linux-bcache@vger.kernel.org
Subject: Re: bcache and LVM
Date: Tue, 09 Feb 2016 20:09:29 -0800 [thread overview]
Message-ID: <87mvr9tddy.fsf@vostro.rath.org> (raw)
In-Reply-To: <87k2mgo2rz.fsf@vostro.rath.org> (Nikolaus Rath's message of "Sun, 07 Feb 2016 09:20:48 -0800")
On Feb 07 2016, Nikolaus Rath <Nikolaus@rath.org> wrote:
> Hello,
>
> The internet claims that using bcache with LVM is not a good idea
> (eg. on https://wiki.archlinux.org/index.php/Bcache )- but I wasn't able
> to find any substantial information other than this general
> recommendation.
>
> Is this still (or has ever been) correct? If so, what issues can arise?
> And does this happen only when using bcache on top of an LVM LV, or also
> when using a bcache device as an LVM PV?
I now have the following stack:
btrfs on LUKS on LVM on bcache
The VG contains two bcache PVs with backing devices on different
spinning disks, and a shared cache device on SSD. I'm using Kernel 4.3.
I'm super happy with the performance, boot times increased from 1:30
minutes to X11 and 2:00 to Firefox to roughly 0:10 to X11 and 0:30 to
Firefox.
Time will tell if it also keeps my data intact, but I hope btrfs would
at least detect any corruption.
Best,
-Nikolaus
(No Cc on replies please, I'm reading the list)
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-02-10 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 17:20 bcache and LVM Nikolaus Rath
2016-02-08 13:44 ` Jens-U. Mozdzen
2016-02-08 22:02 ` Nikolaus Rath
2016-02-09 10:44 ` Jens-U. Mozdzen
2016-02-09 16:02 ` Nikolaus Rath
2016-02-09 16:35 ` Jens-U. Mozdzen
2016-02-10 4:09 ` Nikolaus Rath [this message]
2016-02-24 7:18 ` bcache and LVM --- works great Eric Wheeler
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=87mvr9tddy.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--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