Has anyone examined this issue as it pertains to the 1-2-mdisk option? No issues cloning my image with LVM partitions on SSDs if doing it a disk at a time, but the one to many results in only one of the many cloning properly. I am using Clonezilla 2.6.7-28.
Edit to add: I tried this with 4 HDDs and got the same behavior as with 4 SDDs. CentOS67 LVM partitions (and data within) are only copied to one of the drives if using 1-2-mdisk option. Is it possible that whatever fix was done for restoredisk regarding LVM partitions wasn't ported into the 1-2-mdisk code?
Last edit: kdieudon 2020-07-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for asking. Due to the LVM limitation, the 1-2-mdisks won't work since on the same machine, if all the LVs have same names, they are messed up. We should improve 1-2-mdisk mode and give prompts about this.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone examined this issue as it pertains to the 1-2-mdisk option? No issues cloning my image with LVM partitions on SSDs if doing it a disk at a time, but the one to many results in only one of the many cloning properly. I am using Clonezilla 2.6.7-28.
Edit to add: I tried this with 4 HDDs and got the same behavior as with 4 SDDs. CentOS67 LVM partitions (and data within) are only copied to one of the drives if using 1-2-mdisk option. Is it possible that whatever fix was done for restoredisk regarding LVM partitions wasn't ported into the 1-2-mdisk code?
Last edit: kdieudon 2020-07-16
Thanks for asking. Due to the LVM limitation, the 1-2-mdisks won't work since on the same machine, if all the LVs have same names, they are messed up. We should improve 1-2-mdisk mode and give prompts about this.
Steven