All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] About --mirrorlog mirrored option in the latest lvm2
@ 2018-10-31  7:18 Gang He
  2018-10-31 10:08 ` Zdenek Kabelac
  0 siblings, 1 reply; 3+ messages in thread
From: Gang He @ 2018-10-31  7:18 UTC (permalink / raw)
  To: linux-lvm

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.

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

 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [linux-lvm] About --mirrorlog mirrored option in the latest lvm2
  2018-10-31  7:18 [linux-lvm] About --mirrorlog mirrored option in the latest lvm2 Gang He
@ 2018-10-31 10:08 ` Zdenek Kabelac
  0 siblings, 0 replies; 3+ messages in thread
From: Zdenek Kabelac @ 2018-10-31 10:08 UTC (permalink / raw)
  To: LVM general discussion and development, Gang He

Dne 31. 10. 18 v 8:18 Gang He napsal(a):
> 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.
> 
> 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.
> 

Hi

In general -  users should be creating '--type raid1'   mirrors - user get 
this type automatically when asks for a mirrored LV for long time already.
(lvcreate -m1)  (and old --type mirror only when explicitly set with --type 
parameter).

Mirrored log type had several mostly unfixable design issues - thus it's 
support is marked as deprecated - you still can activate it - but you cannot 
create it as a new device anymore.

In practices users should convert type 'raid1' types  (via lvconvert) - since 
its support for log per leg is believed to be better approach and it's also 
faster.

The only remaining place where the old mirror does not have yet replacement is 
clustered mirror with cmirrord - so only here user should keep running old 
mirror type (but it's believed users are shifting to other technologies giving 
better performance i.e. gluster)

Zdenek

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [linux-lvm] About --mirrorlog mirrored option in the latest lvm2
@ 2018-10-31  8:28 Gang He
  0 siblings, 0 replies; 3+ messages in thread
From: Gang He @ 2018-10-31  8:28 UTC (permalink / raw)
  To: linux-lvm

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-10-31 10:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-31  7:18 [linux-lvm] About --mirrorlog mirrored option in the latest lvm2 Gang He
2018-10-31 10:08 ` Zdenek Kabelac
2018-10-31  8:28 Gang He

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.