From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15420] New: EXT4_USE_FOR_EXT23 causes wrong free space calculation on ext2 and ext3
Date: Mon, 1 Mar 2010 18:18:34 GMT [thread overview]
Message-ID: <bug-15420-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=15420
Summary: EXT4_USE_FOR_EXT23 causes wrong free space calculation
on ext2 and ext3
Product: File System
Version: 2.5
Kernel Version: 2.6.33
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: thomas@archlinux.org
Regression: No
When enabling the EXT4_USE_FOR_EXT23 option in 2.6.33. The free space
calculation on ext2 and ext3 becomes incorrect. Steps to reproduce:
1) Create ext2 or ext3 file system with mkfs
2) Mount it on a kernel with EXT4_USE_FOR_EXT23 enabled
3) Launch "watch -n1 df -h /path/to/mountpoint" in another terminal
4) Download a file with wget
The "used space" on the ext2/3 will now increase by about 500MB per second.
Once you stop the download and type "sync" (or wait for a while), the values
shown for free/used space return to expected values. This is always
reproducible.
We can reproduce this on x86_32 and x86_64 with the Arch Linux distribution
kernel, as well as my own personal Core2-optimized 64 Bit kernel.
.config x86_32:
http://repos.archlinux.org/wsvn/packages/kernel26/trunk/config?rev=70484
.config x86_64:
http://repos.archlinux.org/wsvn/packages/kernel26/trunk/config.x86_64?rev=70484
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-03-01 18:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 18:18 bugzilla-daemon [this message]
2010-03-01 18:19 ` [Bug 15420] EXT4_USE_FOR_EXT23 causes wrong free space calculation on ext2 and ext3 bugzilla-daemon
2010-03-09 21:27 ` bugzilla-daemon
2010-03-09 21:35 ` bugzilla-daemon
2010-03-09 22:07 ` bugzilla-daemon
2010-03-10 3:12 ` bugzilla-daemon
2010-03-10 11:29 ` Jan Kara
2010-03-10 12:25 ` bugzilla-daemon
2010-03-10 12:36 ` bugzilla-daemon
2010-03-10 14:16 ` bugzilla-daemon
2010-03-10 14:18 ` bugzilla-daemon
2010-03-10 14:56 ` bugzilla-daemon
2010-03-10 15:11 ` bugzilla-daemon
2010-03-10 15:28 ` bugzilla-daemon
2010-03-10 15:44 ` bugzilla-daemon
2010-03-11 16:00 ` bugzilla-daemon
2010-03-11 16:01 ` bugzilla-daemon
2010-03-11 16:10 ` bugzilla-daemon
2010-03-11 16:17 ` bugzilla-daemon
2010-03-11 17:42 ` bugzilla-daemon
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=bug-15420-13602@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.