On 9/7/20 10:32 PM, Zdenek Kabelac wrote:
Dne 05. 09. 20 v 11:08 heming.z...@suse.com napsal(a):
On 9/5/20 5:06 PM, Zhao Heming wrote:
report LV is usable for upper layer.
Signed-off-by: Zhao Heming
---
lib/activate/activate.h | 2 +
lib/activate/dev_manager.c | 67 ++
Hi Mikulas,
Thanks for the replies
I am confused now with the last message?
LVM doesn't support taking existing cow device and attaching it to an
existing volume?
Isn't that what "lvconvert --splitsnapshot" & "lvconvert -s" is ment to
be doing?
lets say that I create the snapshot on a dif
it worked
I missed the -Zn flag
Sent from my iPhone
> On 7 Sep 2020, at 21:56, Tomas Dalebjörk wrote:
>
> hi
> I tried all these steps
> but when I associated the snapshot cow device back to an empty origin, and
> typed the lvs command
> the data% output shows 0% instead of 37% ?
> so it l
yes,
we need the snapshot data, as it is provisioned from the backup target and
can’t be changed
we will definitely look into thin snapshots later, but want to first making
sure that we can reanimate the cow device as a device and associate this with
an empty origin
we want if possible be abl
hi
I tried all these steps
but when I associated the snapshot cow device back to an empty origin, and
typed the lvs command
the data% output shows 0% instead of 37% ?
so it looks like that the lvconvert -s vg1/lvsnap vg1/lv0 looses the cow data?
perhaps ypu can guide me how this can be done?
bt
Dne 07. 09. 20 v 19:37 Tomas Dalebjörk napsal(a):
thanks
ok
vgsplit/merge instead
and after that lvconvert-s
yes, I am aware of the issues with corruption
but if the cow device has all data, than no corruption will happen, right?
if COW has a copy of all blocks
than a lvconvert —merge, or mo
thanks
ok
vgsplit/merge instead
and after that lvconvert-s
yes, I am aware of the issues with corruption
but if the cow device has all data, than no corruption will happen, right?
if COW has a copy of all blocks
than a lvconvert —merge, or mount of the snapshot volume will be without issues
r
Dne 07. 09. 20 v 18:34 Tomas Dalebjörk napsal(a):
thanks for feedback
so if I understand this correctly
# fallocate -l 100M /tmp/pv1
# fallocate -l 100M /tmp/pv2
# fallocate -l 100M /tmp/pv3
# losetup —find —show /tmp/pv1
# losetup —find —show /tmp/pv2
# losetup —find —show /tmp/pv3
# vgcreate
thanks for feedback
so if I understand this correctly
# fallocate -l 100M /tmp/pv1
# fallocate -l 100M /tmp/pv2
# fallocate -l 100M /tmp/pv3
# losetup —find —show /tmp/pv1
# losetup —find —show /tmp/pv2
# losetup —find —show /tmp/pv3
# vgcreate vg0 /dev/loop0
# lvcreate -n lv0 -l 1 vg0
# vgexte
Dne 05. 09. 20 v 11:08 heming.z...@suse.com napsal(a):
On 9/5/20 5:06 PM, Zhao Heming wrote:
report LV is usable for upper layer.
Signed-off-by: Zhao Heming
---
lib/activate/activate.h | 2 +
lib/activate/dev_manager.c | 67
lib/metadata/metadata-exp
Dne 07. 09. 20 v 16:14 Dalebjörk, Tomas napsal(a):
Hi Mikulas,
Thanks for the replies
I am confused now with the last message?
LVM doesn't support taking existing cow device and attaching it to an existing
volume?
Isn't that what "lvconvert --splitsnapshot" & "lvconvert -s" is ment to be
d
On Fri, 4 Sep 2020, Tomas Dalebjörk wrote:
> 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
> #
On 9/5/20 5:06 PM, Zhao Heming wrote:
> report LV is usable for upper layer.
>
> Signed-off-by: Zhao Heming
> ---
> lib/activate/activate.h | 2 +
> lib/activate/dev_manager.c | 67
> lib/metadata/metadata-exported.h | 1 +
> lib/metadata/metadata.c
13 matches
Mail list logo
