From: Roman Mamedov <rm@romanrm.net>
To: antlists <antlists@youngman.org.uk>
Cc: Ram Ramesh <rramesh2400@gmail.com>,
"R. Ramesh" <rramesh@verizon.net>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Best way to add caching to a new raid setup.
Date: Sat, 29 Aug 2020 20:57:35 +0500 [thread overview]
Message-ID: <20200829205735.58dfcda1@natsu> (raw)
In-Reply-To: <6a9fc5ae-1cae-a3d6-6dc3-d1a93dc1e38e@youngman.org.uk>
On Sat, 29 Aug 2020 16:34:56 +0100
antlists <antlists@youngman.org.uk> wrote:
> On 28/08/2020 21:39, Ram Ramesh wrote:
> > 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?
>
> Simplicity says have ONE raid, with ONE PV on top of it.
>
> The other way round is you need TWO SEPARATE (at least) PV/VG/LVs, which
> you then stick a raid on top.
I believe the question was not about the order of layers, but whether to
create a RAID with mdadm and then LVM on top, vs. abandoning mdadm and using
LVM's built-in RAID support instead:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/logical_volume_manager_administration/mirror_create
Personally I hugely prefer mdadm, due to the familiar and convenient interface
of the program itself, as well as of /proc/mdstat.
--
With respect,
Roman
next prev parent reply other threads:[~2020-08-29 15:57 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
2020-08-29 15:34 ` antlists
2020-08-29 15:57 ` Roman Mamedov [this message]
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=20200829205735.58dfcda1@natsu \
--to=rm@romanrm.net \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rramesh2400@gmail.com \
--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 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.