From: "R. Ramesh" <rramesh@verizon.net>
To: Linux Raid <linux-raid@vger.kernel.org>
Subject: Best way to add caching to a new raid setup.
Date: Thu, 27 Aug 2020 21:31:07 -0500 [thread overview]
Message-ID: <16cee7f2-38d9-13c8-4342-4562be68930b@verizon.net> (raw)
In-Reply-To: 16cee7f2-38d9-13c8-4342-4562be68930b.ref@verizon.net
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.
Is anyone of them better than other or no cache is safer. Since I
switched over to NVME boot drives, I have quite a few SATA SSDs lying
around that I can put to good use, if I cache using them.
I will move to xubuntu 20.04 as part of this upgrade. So, hopefully, I
will have recent versions of kernel, mdadm and fstools. With these I
should be able to make full use of current features, if any is needed
for caching support.
Please let me know your expert opinion.
Thanks
Ramesh
next parent reply other threads:[~2020-08-28 2:31 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 ` R. Ramesh [this message]
2020-08-28 3:05 ` Best way to add caching to a new raid setup 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
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=16cee7f2-38d9-13c8-4342-4562be68930b@verizon.net \
--to=rramesh@verizon.net \
--cc=linux-raid@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).