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: Tue, 31 Jul 2018 21:33:13 -0400 [thread overview]
Message-ID: <23393.3545.410050.534764@quad.stoffel.home> (raw)
In-Reply-To: <CAJCQCtSmBF68LbvCF=qNT5hePaYFOcF7=jB8=MERXBvA-FUMhQ@mail.gmail.com>
>>>>> "Chris" == Chris Murphy <lists@colorremedies.com> writes:
Chris> On Fri, Jul 27, 2018 at 1:31 PM, John Stoffel <john@stoffel.org> wrote:
>>
>> 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.
Chris> Btrfs supports grow and shrink resizes only when mounted. It's
Chris> not possible to resize when unmounted.
That's... bizarre. Good to know, but bizarre. That does make it more
appealing to use in day to day situations for sure. Any thoughts on
how stable this is in real life?
John
next prev parent reply other threads:[~2018-08-01 1:33 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 [this message]
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=23393.3545.410050.534764@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).