From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Demi Marie Obenour <demi@invisiblethingslab.com>
Subject: Re: [linux-lvm] Running thin_trim before activating a thin pool
Date: Sun, 30 Jan 2022 21:22:00 +0100 [thread overview]
Message-ID: <629a699cb96d9be06152fc7fffac235a@assyoma.it> (raw)
In-Reply-To: <b66e90ec-28ed-3962-ac99-69f8e1b01936@gmail.com>
Il 2022-01-30 12:18 Zdenek Kabelac ha scritto:
> Thin is more oriented towards extreme speed.
> VDO is more about 'compression & deduplication' - so space efficiency.
>
> Combining both together is kind of harming their advantages.
Unfortunately, it is the only (current) solution to have snapshotting
with data compression/deduplication.
Integrating snapshot capability into VDO would be awesome!
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
_______________________________________________
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/
next prev parent reply other threads:[~2022-01-30 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 18:52 [linux-lvm] Running thin_trim before activating a thin pool Demi Marie Obenour
2022-01-29 19:42 ` Zdenek Kabelac
2022-01-29 20:09 ` Demi Marie Obenour
2022-01-29 21:40 ` Zdenek Kabelac
2022-01-30 1:20 ` Demi Marie Obenour
2022-01-30 11:18 ` Zdenek Kabelac
2022-01-30 17:30 ` Demi Marie Obenour
2022-01-30 17:56 ` Zdenek Kabelac
2022-01-30 18:01 ` Demi Marie Obenour
2022-01-30 18:42 ` Zdenek Kabelac
2022-01-30 20:22 ` Gionatan Danti [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-29 17:45 Demi Marie Obenour
2022-01-31 11:02 ` Gionatan Danti
2022-01-31 13:41 ` Zdenek Kabelac
2022-01-31 14:12 ` Gionatan Danti
2022-01-31 15:28 ` Demi Marie Obenour
2022-01-31 17:54 ` Gionatan Danti
2022-01-31 19:04 ` Demi Marie Obenour
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=629a699cb96d9be06152fc7fffac235a@assyoma.it \
--to=g.danti@assyoma.it \
--cc=demi@invisiblethingslab.com \
--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).