From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm-vdo, snapshots and cache
Date: Wed, 16 Nov 2022 16:35:48 +0100 [thread overview]
Message-ID: <605a0a83-4403-253a-73e1-e70849178eb7@gmail.com> (raw)
In-Reply-To: <99746334610331ae0f7cca166649fdd0@assyoma.it>
Dne 16. 11. 22 v 15:38 Gionatan Danti napsal(a):
> Il 2022-11-16 11:50 Zdenek Kabelac ha scritto:
>> Well - as said - vg on vg is basically equivalent of the original LV
>> on top of VDO manager.
>
> Hi Zdenek,
> it seems clunkier to manage two nested VG/LV if you ask me.
IMHO not different from lvm on top of vdo managed volume.
It should be mostly equal (and in few cases possibly even easier or at least
more OS friendly)
>
>> But still these fast snapshot do not solve you a problem of double
>> out-of-space fault.
>
> Yeah, but available space requires constant monitor even when dealing with
> lvmthin.
>
>> It's good for experimenting - but I'd not suggest to use this setup.
>
> In RHEL7 it was specifically supported - see here[1]:
>
> "As a general rule, you should place certain storage layers under VDO and
> others on top of VDO:
> Under VDO: DM-Multipath, DM-Crypt, and software RAID (LVM or mdraid).
> On top of VDO: LVM cache, LVM snapshots, and LVM Thin Provisioning"
>
> For a practical example: in the past I experimented with a storage stack
> composed of raid -> vdo -> lvmthin -> xfs serving qemu/kvm virtual disk files.
> The lvmthin layer enabled rolling snapshots, and was a key feature of the test
> setup.
>
> Now the only method to replicate that is to have two nested LVM instances, one
> running vdo and one lvmthin - right?
>
Well - it's not difficult 'coding' to enable using 'VDO LV' as thinpool data
LV, however we currently lack a lot on support for 'VDO LV' recovery alone in
lvm2 - so until this will get polished - we try to avoid shot ourself to our
foots with enabling these complicated stacks ATM :)
We also have some ideas for different snapshoting inside VDO - so we will see
how that will go - it looks more supportable then combining VDO+THIN together.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2022-11-16 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:42 [linux-lvm] lvm-vdo, snapshots and cache Gionatan Danti
2022-11-15 21:56 ` Zdenek Kabelac
2022-11-15 22:41 ` Gionatan Danti
2022-11-16 10:50 ` Zdenek Kabelac
2022-11-16 14:38 ` Gionatan Danti
2022-11-16 15:35 ` Zdenek Kabelac [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=605a0a83-4403-253a-73e1-e70849178eb7@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).