From: Bruce Guenter <bruce@untroubled.org>
To: linux-ext4@vger.kernel.org
Subject: Re: ext4 df regression introduced by commit 9d0be50
Date: Thu, 20 May 2010 10:32:14 -0600 [thread overview]
Message-ID: <20100520163214.GC28770@untroubled.org> (raw)
In-Reply-To: <20100520161121.GB28963@atrey.karlin.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Thu, May 20, 2010 at 06:11:21PM +0200, Jan Kara wrote:
> Hmm, I'm not seeing anything obviously wrong with that patch but
> apparently the number of blocks reserved for delayed allocation is
> miscomputed by a lot...
IIRC this only affects NFS clients. The same test running locally on
the server doesn't show the same problem. I will retest shortly and
confirm (and also test with 2.6.34).
> Is your ext4 filesystem create from scratch or converted from ext3?
I converted from ext3.
> Is
> your application using lots of different files or rather a couple of small
> ones?
The application writes over NFS two files using writev. One is
currently about 38MB and the other is under 1MB.
The "application" FWIW is saving games over NFS from Wesnoth. At least
that's the most obvious application I have found that can reliably
trigger the problem. I did notice the problem at several times when the
game was not even running, but couldn't pin down what else was
happening.
> Anyways a reproducing program would be the best in this case...
I will try to code something up to reproduce the symptoms using the
system call trace as a reference.
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-20 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 18:05 ext4 df regression introduced by commit 9d0be50 Bruce Guenter
2010-05-20 16:11 ` Jan Kara
2010-05-20 16:32 ` Bruce Guenter [this message]
2010-05-20 20:59 ` Bruce Guenter
2010-05-20 23:32 ` 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=20100520163214.GC28770@untroubled.org \
--to=bruce@untroubled.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;
as well as URLs for NNTP newsgroup(s).