Re: [linux-lvm] Raid1 -> linear conversion = destroyed data

["Jason Warr" <jason@warr.net>]

On Thu, 11 Dec 2014 08:17:03 -0600, Phillip Susi <psusi@ubuntu.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/10/2014 8:50 PM, Jason Warr wrote:
>> It ignores the name because what it does with "--trackchanges" is
>> rename the mirror leg to a visible & read only version of the meta.
>> Sample:
>
> You mean it changes the flags to visible and read only.  I don't see
> why it can't rename it as well.
>

Yes, visible and ro is what I meant.

>> You can't track changes and rename the "backup" leg at the same
>> time. If you wanted to keep the backup leg after making sure the in
>> use one was good you would need to issue a new "--splitmirror"
>> command with a new volume name and *no* "--trackchanges" option.
>
> Why not?  A name is just a name; it does not *have* to be called
> origin_rimage_0.

I don't disagree but it is the way the tool works.  My best guess is the  
name is ignored because when you issue "--trackchanges" it is not really  
splitting off the leg, more of off lining it from the perspective of the  
mirror.  It was likely a developer decision for lvconvert to do it that  
way when adding in RAID1 from the md stack.

The documentation for lvconvert could be more clear about it.

>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
>
> iQEcBAEBAgAGBQJUiadfAAoJENRVrw2cjl5Rt+kH/2edRv5pygm91ULcpZ9ehRuW
> 9bB0CpjyrLEp/f8bdqkcoyR2cpcuM2kUXBstvn7YLgyJnBdm8JNt6gZnanJLQ0gr
> CXx6Tu2OQfp87NTbUDqJOLku6EaAQ053zQAoBgnIctFaCUGU+hC1L3iwdkYGnVwZ
> uTdY0C3/t7ShPDvXqTrIqNugqOj7NFAptpENzxBavrkaIp5w47fvVHpWwFpwO3sU
> CheSV+gpqHKlc6T6DfZlDCcCnZHKmMhXzs4EigNZIZFzM8INhn01mJ64tUJKNET7
> eLvqIH8labOqAp4PVFido6Kgl6K/BKvGbzGJcqE9IR2V23yvzRHjretAGnFwed4=
> =sGDQ
> -----END PGP SIGNATURE-----