From: Sandon Van Ness <sandon@van-ness.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Theodore Tso <tytso@MIT.EDU>, linux-ext4@vger.kernel.org
Subject: Re: ext4 df free space reporting not reliable?
Date: Sun, 13 Jun 2010 09:45:35 -0700 [thread overview]
Message-ID: <4C150B2F.7040208@van-ness.com> (raw)
In-Reply-To: <20100613103451.GF31464@basil.fritz.box>
On 06/13/2010 03:34 AM, Andi Kleen wrote:
>> Are you creating the files as root? Sounds like the standard reserved
>> blocks behavior that's been around since ext3, ext2, BSD's ufs, etc...
>>
> Yes everything is root.
>
> I would expect root df to not report the reservation. Is that not the case?
>
> -Andi
>
Is the root reserve (default 5% on ext3, not sure for ext3) set to 0?
tune2fs -m0 /dev/sdX
The file-system does not need to be unmounted to do this but this will
change the amount reported as available as once it hits 0 with the root
reserve only root can write to the FS.
next prev parent reply other threads:[~2010-06-13 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 9:38 ext4 df free space reporting not reliable? Andi Kleen
2010-06-13 10:27 ` Theodore Tso
2010-06-13 10:34 ` Andi Kleen
2010-06-13 16:45 ` Sandon Van Ness [this message]
2010-06-13 18:58 ` tytso
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=4C150B2F.7040208@van-ness.com \
--to=sandon@van-ness.com \
--cc=andi@firstfloor.org \
--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