From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: how to scale root-reserved space going forward...
Date: Mon, 02 Mar 2009 10:26:21 -0600 [thread overview]
Message-ID: <49AC08AD.7050602@redhat.com> (raw)
In-Reply-To: <20090302085632.GM3199@webber.adilger.int>
Andreas Dilger wrote:
> I suspect that at a certain filesystem size, there isn't much benefit
> in having more reserved space. If we keep 50GB of reserved space then
> this is likely to contain a decent amount of 1MB free chunks, which is
> what we really care about.
>
> Cheers, Andreas
As long as we don't care much about inode<->block locality, that is
probably ok...
I got one off-list reply from someone who was depending on the 5% for
administration reasons, but even if we change the default I assume we'll
leave the tunable in place for people who really do want 5% for
"root-reserved" over "allocator safety buffer" reasons.
-Eric
prev parent reply other threads:[~2009-03-02 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 22:22 how to scale root-reserved space going forward Eric Sandeen
2009-03-02 2:47 ` Theodore Tso
2009-03-02 7:17 ` Ron Johnson
2009-03-02 8:56 ` Andreas Dilger
2009-03-02 16:26 ` Eric Sandeen [this message]
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=49AC08AD.7050602@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).