linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <dchg2000@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] About --mirrorlog mirrored option in the latest lvm2
Date: Wed, 31 Oct 2018 16:28:51 +0800	[thread overview]
Message-ID: <CAGmFzSeAiJ_Rn-shYG3K1VBcVxxy9RjLG7ZeOL-aHKQDpzC+RA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

Hello List,

As you know, in the past versions(e.g. v2.02.120), lvcreate supports
creating a mirror type LV with "--mirrorlog mirrored" option,
But in the latest versions(e.g. v2.02.180), lvm2 says "mirrored is a
persistent log that is itself mirrored, but should be avoided. Instead, use
the raid1 type for log redundancy."
Then,  my questions are as below,
1)The latest lvm2 does not allow creating this kind of LV, or just not
recommended?
In my test environment, it looks that LVM2 can not create this kind of LV.
tb0307-nd1:/ # lvcreate --type mirror -m1 --mirrorlog mirrored -L 2G -n
mirr-lv cluster-vg2
  Log type, "mirrored", is unavailable to cluster mirrors.
If I try to create this kind of LV in local VG (not cluster VG), this
operation will be supported?

2)If we can not create this kind of LV, how can we migrate these existing
LVs after we upgrade LVM2 to the latest version (e.g. v2.02.180)?
e.g. we need to convert this kind of LV to "RAID1 type LV, I want to know
if there is a suggested guide for this scenario.

Thanks
Gang

[-- Attachment #2: Type: text/html, Size: 2325 bytes --]

             reply	other threads:[~2018-10-31  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  8:28 Gang He [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-31  7:18 [linux-lvm] About --mirrorlog mirrored option in the latest lvm2 Gang He
2018-10-31 10:08 ` Zdenek Kabelac

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=CAGmFzSeAiJ_Rn-shYG3K1VBcVxxy9RjLG7ZeOL-aHKQDpzC+RA@mail.gmail.com \
    --to=dchg2000@gmail.com \
    --cc=linux-lvm@redhat.com \
    /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).