From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Marc MERLIN <marc@merlins.org>
Subject: Re: [linux-lvm] Why use thin_pool_autoextend_threshold < 100 ?
Date: Tue, 31 Jul 2018 14:35:42 +0200 [thread overview]
Message-ID: <c086c2e3-8b84-76a6-129a-0bad04bb849f@redhat.com> (raw)
In-Reply-To: <20180731024410.v3ovzjth4svrus6y@merlins.org>
Dne 31.7.2018 v 04:44 Marc MERLIN napsal(a):
> On Fri, Jul 27, 2018 at 11:26:58AM -0700, Marc MERLIN wrote:
>> Hi Zdenek,
>>
>> Thanks for your helpful reply.
>
> Ha again Zdenek,
>
> Just to confirm, am I going to be ok enough with the scheme I described
> as long as I ensure that 'Allocated pool data' does not get to 100% ?
>
> For now, I have my btrfs filesystems mounted with "discard", so
> hopefully it should tell dm-thin when it can free up/reuse blocks.
>
> Given that, am I more or less ok using dm-thin that way?
>
> And for my own understanding, is there any reason why I would even want
> to consider thin_pool_autoextend_threshold < 100 ?
>
Hi
If you monitor amount of free space for data AND for metadata in thin-pool
yourself you can keep easily threshold == 100.
Just don't forget when you upsize 'data' - you should also typically
extend also metadata - it's not uncommon issue user start with small
'data' & 'metadata' LV with thin-pool - then continue to only extend
thin-pool 'data' volume and ignore/forget about metadata completely
and hit the full metadata device - which can lead to many troubles
(hitting full dataLV is normally not a big deal).
Regards
Zdenek
next prev parent reply other threads:[~2018-07-31 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 16:31 [linux-lvm] Why use thin_pool_autoextend_threshold < 100 ? Marc MERLIN
2018-07-27 12:59 ` Zdenek Kabelac
2018-07-27 18:26 ` Marc MERLIN
2018-07-27 19:31 ` John Stoffel
2018-07-27 19:58 ` Marc MERLIN
2018-07-27 21:09 ` John Stoffel
2018-07-27 23:35 ` Marc MERLIN
2018-07-31 4:52 ` Chris Murphy
2018-08-01 1:33 ` John Stoffel
2018-08-01 2:43 ` Chris Murphy
2018-08-02 17:42 ` Chris Murphy
2018-07-31 2:44 ` Marc MERLIN
2018-07-31 12:35 ` Zdenek Kabelac [this message]
2018-07-31 21:17 ` Marc MERLIN
2018-08-01 11:37 ` 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:
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=c086c2e3-8b84-76a6-129a-0bad04bb849f@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=marc@merlins.org \
/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).