From: Chris Friesen <chris.friesen@windriver.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] about the lying nature of thin
Date: Fri, 29 Apr 2016 15:37:00 -0500 [thread overview]
Message-ID: <5723C5EC.6020903@windriver.com> (raw)
In-Reply-To: <1009262601.20160429104420@marki-online.net>
On 04/29/2016 03:44 AM, Marek Podmaka wrote:
> Now I'm not sure what your use-case for thin pools is.
>
> I don't see it much useful if the presented space is smaller than
> available physical space. In that case I can just use plain LVM with
> PV/VG/LV. For snaphosts you don't care much as if the snapshot
> overfills, it just becomes invalid, but won't influence the original
> LV.
One useful case for "presented space equal to physical space" with thin volumes
is that it simplifies security issues.
With raw LVM volumes I generally need to zero out the whole volume prior to
deleting it (to avoid leaking the contents to other users). This takes time,
and also seriously hammers the disks when you have multiple volumes being zeroed
in parallel.
With thin, deletion is essentially instantaneous, and the zeroing penalty is
paid when the disk block is actually written. Any disk blocks which have not
been written are simply read as all-zeros.
Chris
next prev parent reply other threads:[~2016-04-29 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:37 [linux-lvm] about the lying nature of thin Xen
2016-04-29 8:44 ` Marek Podmaka
2016-04-29 10:06 ` Gionatan Danti
2016-04-29 13:16 ` Xen
2016-04-29 22:32 ` Xen
2016-04-30 4:46 ` Mark Mielke
2016-05-03 13:03 ` Xen
2016-04-29 11:53 ` Xen
2016-04-29 20:37 ` Chris Friesen [this message]
2016-05-10 21:47 ` [linux-lvm] thin disk -- like overcomitted/virtual memory? (was Re: about the lying nature of thin) Linda A. Walsh
2016-05-10 23:58 ` Xen
[not found] <1714078834.3820492.1461944731537.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-29 15:45 ` [linux-lvm] about the lying nature of thin matthew patton
2016-05-02 13:18 ` Mark H. Wood
2016-05-03 11:57 ` Xen
[not found] <1093625508.5537728.1462283037119.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-03 13:43 ` matthew patton
2016-05-03 17:42 ` Xen
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=5723C5EC.6020903@windriver.com \
--to=chris.friesen@windriver.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).