From: Xen <list@xenhideout.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] about the lying nature of thin
Date: Fri, 29 Apr 2016 15:16:12 +0200 [thread overview]
Message-ID: <ba7cee20dbf40157dcff5746cbef9158@dds.nl> (raw)
In-Reply-To: <5723322A.3060702@assyoma.it>
Gionatan Danti schreef op 29-04-2016 12:06:
> Let me add one important use case: have fast, flexible snapshots.
One more huge reason for using it in a desktop system.
I didn't know about the performance benefits.
I just know that providing snapshot space in advance by registering in
advance LVs for that purpose, is not a good way of working (for me, or
anyone).
Although the idea of using LVM thin to provide only a single thin volume
might be rather odd ;-).
Still, the snapshotting is clearly superior to that of traditional LVM,
right?
Regards.
next prev parent reply other threads:[~2016-04-29 13:16 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 [this message]
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
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=ba7cee20dbf40157dcff5746cbef9158@dds.nl \
--to=list@xenhideout.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.