<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">hi<div><br></div><div>I tried to perform as suggested</div><div># lvconvert —splitsnapshot vg/lv-snap</div><div>works fine</div><div># lvconvert -s vg/lv vg/lv-snap</div><div>works fine too</div><div><br></div><div>but...</div><div>if I try to converting cow data directly from the meta device, than it doesn’t work</div><div>eg</div><div># lvconvert -s vg/lv /dev/mycowdev</div><div>the tool doesn’t like the path</div><div>I tried to place a link in /dev/vg/mycowdev -> /dev/mycowdev</div><div>and retried the operations </div><div># lvconveet -s vg/lv /dev/vg/mycowdev</div><div>but this doesn’t work either</div><div><br></div><div>conclusion </div><div>even though the cow device is an exact copy of the cow device that I have saved on /dev/mycowdev before the split, it wouldn’t work to use to convert back as a lvm snapshot </div><div><br></div><div>not sure if I understand the tool correctly, or if there are other things needed to perform, such as creating virtual information about the lvm VGDA data on the first of this virtual volume named /dev/mycowdev </div><div><br></div><div>let me know what more steps are needed</div><div><br></div><div>beat regards Tomas</div><div><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On 7 Nov 2019, at 18:29, Tomas Dalebjörk <tomas.dalebjork@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Great, thanks! <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Den tors 7 nov. 2019 kl 17:54 skrev Mikulas Patocka <<a href="mailto:mpatocka@redhat.com">mpatocka@redhat.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> <br> On Tue, 5 Nov 2019, Tomas Dalebjörk wrote:<br> <br> > Thanks,<br> > <br> > That really helped me to understand how the snapshot works.<br> > Last question:<br> > - lets say that block 100 which is 1MB in size is in the cow device, and a write happen that wants to something or all data on that region of block 100.<br> > Than I assume; based on what have been previously said here, that the block in the cow device will be overwritten with the new changes.<br> <br> Yes, the block in the cow device will be overwritten.<br> <br> Mikulas<br> <br> > Regards Tomas</blockquote></div> </div></blockquote></div></body></html>