From: "John Stoffel" <john@stoffel.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] Why use thin_pool_autoextend_threshold < 100 ?
Date: Fri, 27 Jul 2018 15:31:36 -0400 [thread overview]
Message-ID: <23387.29464.233937.89557@quad.stoffel.home> (raw)
In-Reply-To: <20180727182658.GI23157@merlins.org>
>>>>> "Marc" == Marc MERLIN <marc@merlins.org> writes:
Marc> Hi Zdenek,
Marc> Thanks for your helpful reply.
Marc> On Fri, Jul 27, 2018 at 02:59:28PM +0200, Zdenek Kabelac wrote:
>> Dne 26.7.2018 v 18:31 Marc MERLIN napsal(a):
>> >Still learning about thin volumes.
>> >Why do I want my thin pool to get auto extended? Does "extended" mean
>> >resized?
>>
>> yes extension == resize
Marc> Gotcha. Then I don't want to have to worry about my filesystem being resized
Marc> multiple times, especially since I'm not sure how it will help.
>> man lvmthin.
Marc> Thanks. Had read it, but not carefully enough.
Marc> So, I just re-read "Automatic extend settings"
Marc> I'm still I'm not entirely sure how using extension would help me there. I
Marc> can't set it to 10% for all 10 filesystems (50% is minimum).
Marc> If I set it to anything less than 100%, it could later that it can block,
Marc> and try to extend and resize later, but ultimately I'll still have multiple
Marc> filesystems that together exceed the space available, so I can run out.
Marc> I'm not seeing how the automatic extend setting is helpful, at least in my case.
Marc> Am I missing something?
Marc> To be clear, my case is that I will have 10 filesystems in a
Marc> place where the same data was in a single filesystem that sadly
Marc> I must segment now. More than a few will take more than 1/10th
Marc> of the space, but I don't want to have to worry about which ones
Marc> are going to use how much as long as all together they stay
Marc> below 100% of course.
Marc> I don't want to have to manage space for each of those 10 and
Marc> have to resize them by hand multiple times up and down to share
Marc> the space, hence dm-thin.
Why don't you run quotas on your filesystems? Also, none of the
filesystems in Linux land that I'm aware of supports shrinking the
filesystem while live, it's all a unmount, shrink FS, shrink volume
(carefully!) and then re-mount the filesystem.
But again, I think you might really prefer quotas instead, unless you
need complete logical seperation.
John
next prev parent reply other threads:[~2018-07-27 19:31 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 [this message]
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
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=23387.29464.233937.89557@quad.stoffel.home \
--to=john@stoffel.org \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@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).