From: David Chinner <dgc@sgi.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Wrong free space reported for XFS filesystem
Date: Thu, 7 Sep 2006 09:02:38 +1000 [thread overview]
Message-ID: <20060906230238.GJ5737019@melbourne.sgi.com> (raw)
In-Reply-To: <9a8748490609060154ye8730b0n16e23524010a35e4@mail.gmail.com>
On Wed, Sep 06, 2006 at 10:54:34AM +0200, Jesper Juhl wrote:
> For your information;
>
> I've been running a bunch of benchmarks on a 250GB XFS filesystem.
> After the benchmarks had run for a few hours and almost filled up the
> fs, I removed all the files and did a "df -h" with interresting
> results :
>
> /dev/mapper/Data1-test
> 250G -64Z 251G 101% /mnt/test
>
> "df -k" reported this :
>
> /dev/mapper/Data1-test
> 262144000 -73786976294838202960 262147504 101% /mnt/test
....
> The filesystem is mounted like this :
>
> /dev/mapper/Data1-test on /mnt/test type xfs
> (rw,noatime,ihashsize=64433,logdev=/dev/Log1/test_log,usrquota)
So the in-core accounting has underflowed by a small amount but the
on disk accounting is correct.
We've had a few reports of this that I know of over the past couple of years,
but we've never managed to find a reproducable test case for it.
Can you describe what benchmark you were runnin, wht kernel you were
using and whether any of the tests hit an ENOSPC condition?
Also, in future can you cc xfs@oss.sgi.com on XFS bug reports?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next parent reply other threads:[~2006-09-06 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a8748490609060154ye8730b0n16e23524010a35e4@mail.gmail.com>
2006-09-06 23:02 ` David Chinner [this message]
[not found] ` <9a8748490609070717q6ed9111ckdc3de025dc44938b@mail.gmail.com>
2006-09-08 2:33 ` Wrong free space reported for XFS filesystem David Chinner
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=20060906230238.GJ5737019@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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