From: Ram Ramesh <rramesh2400@gmail.com>
To: Roman Mamedov <rm@romanrm.net>, "R. Ramesh" <rramesh@verizon.net>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Best way to add caching to a new raid setup.
Date: Fri, 28 Aug 2020 15:39:45 -0500 [thread overview]
Message-ID: <448afb39-d277-445f-cc42-2dfc5210da7b@gmail.com> (raw)
In-Reply-To: <20200828224616.58a1ad6c@natsu>
On 8/28/20 12:46 PM, Roman Mamedov wrote:
> On Thu, 27 Aug 2020 21:31:07 -0500
> "R. Ramesh" <rramesh@verizon.net> wrote:
>
>> I have two raid6s running on mythbuntu 14.04. The are built on 6
>> enterprise drives. So, no hd issues as of now. Still, I plan to upgrade
>> as it has been a while and the size of the hard drives have become
>> significantly larger (a indication that my disks may be older) I want to
>> build new raid using the 16/14tb drives. Since I am building new raid, I
>> thought I could explore caching options. I see a mention of LVM cache
>> and few other bcache/xyzcache etc.
> Once you set up bcache, it cannot be removed. The volume will always stay a
> bcache volume, even if you decide to stop using caching. Which feels weird and
> potentially troublesome, going through an extra layer (kernel driver) with its
> complexity and computational overhead (no matter how small).
>
> On the other hand LVM with caching turned off is just normal LVM, that you'd
> likely would have used anyway, for other benefits that it provides.
>
> Also my impression is that LVM has more solid and reliable codebase, but
> bcache might provide a somewhat better the performance boost due to caching.
>
Thanks for the info on bcache. I do not think it will be my favorite. I
am going to try LVM cache as my first choice. Note that the new disks
will be spare disks for some time and I will be able to try out a few
things before deciding to put it into use.
One thing about LVM that I am not clear. Given the choice between
creating /mirror LV /on a VG over simple PVs and /simple LV/ over raid1
PVs, which is preferred method? Why?
Ramesh
next prev parent reply other threads:[~2020-08-28 20:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16cee7f2-38d9-13c8-4342-4562be68930b.ref@verizon.net>
2020-08-28 2:31 ` Best way to add caching to a new raid setup R. Ramesh
2020-08-28 3:05 ` Peter Grandi
2020-08-28 3:19 ` Ram Ramesh
2020-08-28 15:26 ` antlists
2020-08-28 17:25 ` Ram Ramesh
2020-08-28 22:12 ` antlists
2020-08-28 22:40 ` Ram Ramesh
2020-08-28 22:59 ` antlists
2020-08-29 3:08 ` R. Ramesh
2020-08-29 5:02 ` Roman Mamedov
2020-08-29 20:48 ` Ram Ramesh
2020-08-29 21:26 ` Roger Heflin
2020-08-30 0:56 ` Ram Ramesh
2020-08-30 15:42 ` Roger Heflin
2020-08-30 17:19 ` Ram Ramesh
2020-09-11 18:39 ` R. Ramesh
2020-09-11 20:37 ` Roger Heflin
2020-09-11 22:41 ` Ram Ramesh
2020-08-29 0:01 ` Roger Heflin
2020-08-29 3:12 ` R. Ramesh
2020-08-29 22:36 ` Drew
2020-09-01 16:12 ` Ram Ramesh
2020-09-01 17:01 ` Kai Stian Olstad
2020-09-02 18:17 ` Ram Ramesh
2020-09-14 11:40 ` Nix
2020-09-14 14:32 ` Ram Ramesh
2020-09-14 14:48 ` Roger Heflin
2020-09-14 15:08 ` Wols Lists
2020-08-31 19:20 ` Nix
2020-08-28 17:46 ` Roman Mamedov
2020-08-28 20:39 ` Ram Ramesh [this message]
2020-08-29 15:34 ` antlists
2020-08-29 15:57 ` Roman Mamedov
2020-08-29 16:26 ` Roger Heflin
2020-08-29 20:45 ` Ram Ramesh
2020-08-30 22:16 ` Michal Soltys
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=448afb39-d277-445f-cc42-2dfc5210da7b@gmail.com \
--to=rramesh2400@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=rramesh@verizon.net \
/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).