From: Theodore Tso <tytso@MIT.EDU>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 df free space reporting not reliable?
Date: Sun, 13 Jun 2010 06:27:02 -0400 [thread overview]
Message-ID: <69DFE925-D32D-4CAA-B734-545DE0515FCE@mit.edu> (raw)
In-Reply-To: <20100613093807.GA31407@basil.fritz.box>
On Jun 13, 2010, at 5:38 AM, Andi Kleen wrote:
> Hi,
>
> I have a ext4 file system on 2.6.34 that shows 0 blocks available
> in "df" (it's nearly full but never got a ENOSPC).
>
> But when I delete a couple of files it still shows 0 blocks.
> And I can actually create small files without problem, so clearly
> there is at least some space available.
>
> So is df reporting not accurate?
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...
- Ted
next prev parent reply other threads:[~2010-06-13 10:27 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 [this message]
2010-06-13 10:34 ` Andi Kleen
2010-06-13 16:45 ` Sandon Van Ness
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=69DFE925-D32D-4CAA-B734-545DE0515FCE@mit.edu \
--to=tytso@mit.edu \
--cc=andi@firstfloor.org \
--cc=linux-ext4@vger.kernel.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