archive mirror
 help / color / mirror / Atom feed
From: Joe Thornber <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] Fast thin volume preallocation?
Date: Mon, 3 Jun 2019 14:23:28 +0100	[thread overview]
Message-ID: <20190603132327.GA32187@reti> (raw)
In-Reply-To: <>

On Fri, May 31, 2019 at 03:13:41PM +0200, Gionatan Danti wrote:

> - does standard lvmthin support something similar? If not, how do you see a
> zero coalesce/compression/trim/whatever feature?

There isn't such a feature as yet.  With the next iteration of thin I'd like to
get away from the fixed allocation block sizes that we're using which should greatly
reduce the number of mappings that we need to create to provision a thick volume and
so speed it up a lot.

Presumably you want a thick volume but inside a thin pool so that you can used snapshots?
If so have you considered the 'external snapshot' feature?

> - can I obtain something similar by simply touching (maybe with a 512B only
> write) once each thin chunk?


- Joe

  reply	other threads:[~2019-06-03 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 13:13 [linux-lvm] Fast thin volume preallocation? Gionatan Danti
2019-06-03 13:23 ` Joe Thornber [this message]
2019-06-03 19:23   ` Gionatan Danti
2019-06-03 21:12     ` Ilia Zykov
2019-06-05 10:31       ` Zdenek Kabelac
2019-06-04  5:23     ` Ilia Zykov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190603132327.GA32187@reti \ \ \

* 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).