From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15420] EXT4_USE_FOR_EXT23 causes wrong free space calculation on ext2 and ext3
Date: Wed, 10 Mar 2010 12:36:18 GMT [thread overview]
Message-ID: <201003101236.o2ACaI4a027540@demeter.kernel.org> (raw)
In-Reply-To: <bug-15420-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15420
--- Comment #7 from Thomas Bächler <thomas@archlinux.org> 2010-03-10 12:36:12 ---
(In reply to comment #5)
> This sounds like the block reservation code for delayed allocation is
> over-aggressive about estimating how many blocks are need for the indirect
> blocks in the case of indirect-mapped inodes (which would be what you get when
> mounting an ext2 filesystem using the ext4 file system driver).
>
> This should be an aesthetic issue only, but it would be nice to have this be
> fixed.
It is not purely aesthetic, lots of applications abort their operation if space
is supposedly running low.
However, as this doesn't seem to be high priority for anyone here, we should
probably consider disabling EXT4_USE_FOR_EXT23 in our distribution kernel for
the time being.
(In reply to comment #6)
> Won't it make sence to use 'nodelalloc' by default when ext4 driver is used
> for ext2 or ext3 filesystem? Because delayed allocation has some implications
> people need not expect - like the overestimation of needed blocks, or changed
> semantics of ordered data mode etc...
Don't see a patch here.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-10 12:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 18:18 [Bug 15420] New: EXT4_USE_FOR_EXT23 causes wrong free space calculation on ext2 and ext3 bugzilla-daemon
2010-03-01 18:19 ` [Bug 15420] " 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 [this message]
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
[not found] <bug-15420-13602@https.bugzilla.kernel.org/>
2012-06-18 15:10 ` 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=201003101236.o2ACaI4a027540@demeter.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 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).