From: 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 14:58:59 -0400 [thread overview]
Message-ID: <20100613185858.GB8055@thunk.org> (raw)
In-Reply-To: <20100613103451.GF31464@basil.fritz.box>
On Sun, Jun 13, 2010 at 12:34:51PM +0200, 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?
No, the reservation is always reported, regardless of which user ID is
executing the statfs(2) system call. This has always been true, going
all the way back to BSD 4.3.
I could see the argument for doing this differently, but I could also
see that being very surprising for people to see different results
depending on whether they are running df from a setuid shell or not.
I'm not aware of any Unix system which has implemented the root-only
reservation system which has done this.
- Ted
prev parent reply other threads:[~2010-06-13 18:59 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
2010-06-13 18:58 ` tytso [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=20100613185858.GB8055@thunk.org \
--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