From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Drew Eckhardt <drew.eckhardt2@gmail.com>, linux-lvm@lists.linux.dev
Subject: Re: lvm2/dm-thin snapshot memory and disk overhead
Date: Wed, 16 Oct 2024 13:45:47 +0200 [thread overview]
Message-ID: <5cff8619-087d-473c-86d3-83344e39e02e@gmail.com> (raw)
In-Reply-To: <CAFqQACz8umkccaKVfoECxeCwTghjFP_uVXKXByJ2TL8LEcHYgw@mail.gmail.com>
Dne 12. 10. 24 v 0:46 Drew Eckhardt napsal(a):
> What's the lvm2/dm-thin snapshot memory and disk overhead for each
> chunk (default 64k) overwritten?
>
>
Hi
Depends on the usage.
If you write full 64K block - the whole new provisioned chunk is written.
If you write 1st. 4K block to 'not yet provisioned' chunk for snapshot - then
remains of 64-4 of the origin chunk to be 'copied' to this newly provisioned
chunk.
If you write to already provisioned chunk for a snapshot thin LV - nothing is
copied and all goes just the this chunks.
When origin 'write' to a chunk shared with 'snapshot' - then snapshot will
keep the unmodified chunk and origin gets a new copy with updated content.
Note - snapshot thin LV is just like any other 'thin LV' - it just 'shares'
already allocated chunks with its origin.
Simply said - writing task always 'pays' the price with block update...
Hopefully this makes it clear.
Regards
Zdenek
PS: it's way more efficient compared with old 'thick' snapshots...
prev parent reply other threads:[~2024-10-16 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 22:46 lvm2/dm-thin snapshot memory and disk overhead Drew Eckhardt
2024-10-16 11:45 ` 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=5cff8619-087d-473c-86d3-83344e39e02e@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=drew.eckhardt2@gmail.com \
--cc=linux-lvm@lists.linux.dev \
/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).