From: Andreas Schwab <schwab@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Christopher Friesen <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: discrepency between "df" and "du" on tmpfs filesystem?
Date: Thu, 01 Dec 2005 18:44:00 +0100 [thread overview]
Message-ID: <je4q5s67bz.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0512011634370.26131@goblin.wat.veritas.com> (Hugh Dickins's message of "Thu, 1 Dec 2005 16:41:15 +0000 (GMT)")
Hugh Dickins <hugh@veritas.com> writes:
> On Thu, 1 Dec 2005, Christopher Friesen wrote:
>>
>> Someone noticed this on one of our machines. The rootfs is a 256MB tmpfs
>> filesystem. Depending on how you check the size, you get two different
>> answers.
>>
>> root@10.41.50.66:/root> df -kl
>> rootfs 262144 255684 6460 98% /
>>
>> root@10.41.50.66:/root> du -sxk /
>> 204672 /
>>
>> Anyone know what's going on?
>
> df tells you what the filesystem says is in use or free, via statfs.
> du goes looking at the contents of the filesystem, totalling stats.
> Any files unlinked but held open will be counted by df but not by du.
> There might also be a discrepancy over indirect blocks, I'm not sure.
Also an empty filesystem usually does not have zero use, since the
filesystem overhead (inode table, etc) may be accounted in the statfs
counts.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2005-12-01 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 15:32 Christopher Friesen
2005-12-01 16:41 ` Hugh Dickins
2005-12-01 17:44 ` Andreas Schwab [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=je4q5s67bz.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=cfriesen@nortel.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®