From: Zhiyong Ye <email@example.com>
To: Zdenek Kabelac <firstname.lastname@example.org>,
LVM general discussion and development <email@example.com>
Subject: Re: [linux-lvm] [External] Re: The feasibility of implementing an alternative snapshot approach
Date: Tue, 10 Jan 2023 11:48:50 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Thank you for your patience and explanations. I learned a lot from our
discussions and thank you again for your help.
On 1/10/23 6:18 AM, Zdenek Kabelac wrote:
> Dne 09. 01. 23 v 7:21 Zhiyong Ye napsal(a):
>> Hi Zdenek,
>> Thank you for your detailed answer.
>> For the thin snapshot I will use the latest version of kernel and lvm
>> for further testing. I want to use both snapshot methods (thin and
>> thick) in the production environment. But if the thick snapshot is
>> only still in the maintenance phase, then for thick lv I have to see
>> if there is any other way to accomplish the snapshot function.
> FYI - there are still some delays with up-streaming of the latest
> improvement patches - so stay tuned for further speedup gains & IO
> throughput with thin provisioning)
> By the maintenance phase for old thick snapshot I mean - the development
> of the existing thick snapshot target is basically done - the format is
> very ancient and cannot be changed without major rewrite of the whole
> snapshot target as such - and that's what we've made with newly
> introduced thin-provisioning target which addressed many shortcomings of
> the old dm-snapshot target.
>> I use lvm mainly for virtualized environments. Each lv acts as a block
>> device of the virtual machine. So I also consider using qemu's own
>> snapshot feature. When qemu creates a snapshot, the original image
>> used by the virtual machine becomes read-only, and all write changes
>> are stored in the new snapshot. But currently qemu's snapshots only
>> support files, not block devices.
> Depending on the use-case it might matter to pick the best fitting
> i.e. if the changes are 'localized' in the filesystem areas to match
> thin-pool chunks (also selection of the filesystem itself might be part
> of equation here) - even if you use snapshots a lot, you may eventually
> get better result with bigger chunks like 128k or even 256k size instead
> of default 64K.
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2023-01-10 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 8:00 [linux-lvm] The feasibility of implementing an alternative snapshot approach Zhiyong Ye
2023-01-04 14:09 ` Zdenek Kabelac
2023-01-04 16:12 ` Zhiyong Ye
2023-01-06 13:42 ` Zdenek Kabelac
2023-01-09 6:21 ` Zhiyong Ye
2023-01-09 22:18 ` Zdenek Kabelac
2023-01-10 3:48 ` Zhiyong Ye [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).