<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Mikulas,</p>
<p>Thanks for the replies<br>
</p>
<p>I am confused now with the last message?</p>
<p>LVM doesn't support taking existing cow device and attaching it
to an existing volume?</p>
<p>Isn't that what "lvconvert --splitsnapshot" & "lvconvert -s"
is ment to be doing?</p>
<p>lets say that I create the snapshot on a different device using
these steps:</p>
<font face="Courier New, Courier, monospace">root@src# lvcreate -s
-L 10GB -n lvsnap vg/lv /dev/sdh<br>
root@src# lvconvert ---splitsnapshot vg/lvsnap<br>
root@src# echo "I now move /dev/sdb to another server"<br>
root@tgt# lvconvert -s newvg/newlv vg/lvsnap</font>
<p><br>
</p>
<p>Regards Tomas<br>
</p>
<div class="moz-cite-prefix">Den 2020-09-07 kl. 15:09, skrev Mikulas
Patocka:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.LRH.2.02.2009070907110.5779@file01.intranet.prod.int.rdu2.redhat.com">
<pre class="moz-quote-pre" wrap="">
On Fri, 4 Sep 2020, Tomas Dalebjörk wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">hi
I tried to perform as suggested
# lvconvert —splitsnapshot vg/lv-snap
works fine
# lvconvert -s vg/lv vg/lv-snap
works fine too
but...
if I try to converting cow data directly from the meta device, than it doesn’t work
eg
# lvconvert -s vg/lv /dev/mycowdev
the tool doesn’t like the path
I tried to place a link in /dev/vg/mycowdev -> /dev/mycowdev
and retried the operations
# lvconveet -s vg/lv /dev/vg/mycowdev
but this doesn’t work either
conclusion 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
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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
AFAIK LVM doesn't support taking existing cow device and attaching it to
an existing volume. When you create a snapshot, you start with am empty
cow.
Mikulas
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">let me know what more steps are needed
beat regards Tomas
Sent from my iPhone
On 7 Nov 2019, at 18:29, Tomas Dalebjörk <a class="moz-txt-link-rfc2396E" href="mailto:tomas.dalebjork@gmail.com"><tomas.dalebjork@gmail.com></a> wrote:
Great, thanks!
Den tors 7 nov. 2019 kl 17:54 skrev Mikulas Patocka <a class="moz-txt-link-rfc2396E" href="mailto:mpatocka@redhat.com"><mpatocka@redhat.com></a>:
On Tue, 5 Nov 2019, Tomas Dalebjörk wrote:
> Thanks,
>
> That really helped me to understand how the snapshot works.
> Last question:
> - 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.
> 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.
Yes, the block in the cow device will be overwritten.
Mikulas
> Regards Tomas
</pre>
</blockquote>
</blockquote>
</body>
</html>