archive mirror
 help / color / mirror / Atom feed
From: Paul Dann <>
Subject: [linux-lvm] lvreduce thin-pool
Date: Tue, 14 Jan 2020 09:52:17 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

Hi there,

I've been following Ede Wolf's thread with interest, but it hasn't quite
covered my query, and I've not been able to find much about this in the

Are there any plans to implement reducing of thin pools? I've been bitten
several times by carelessly allowing a thin pool to expand onto unsuitable
storage and subsequently being unable to reduce the pool again to ensure IO
performance of the pool. (I know that better forward planning can mitigate

Mainly, I'm wondering if there are technical reasons this hasn't been
implemented yet? On the face of it, I'd have expected this to be a
relatively straight-forward procedure? But I'd be interested in why this
might not be the case.


[-- Attachment #2: Type: text/html, Size: 905 bytes --]

             reply	other threads:[~2020-01-14  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  9:52 Paul Dann [this message]
2020-01-14 12:21 ` [linux-lvm] lvreduce thin-pool Zdenek Kabelac

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 \ \ \ \

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