[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201003101225.o2ACPVkg024848@demeter.kernel.org>
Date: Wed, 10 Mar 2010 12:25:31 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 15420] EXT4_USE_FOR_EXT23 causes wrong free space calculation
on ext2 and ext3
http://bugzilla.kernel.org/show_bug.cgi?id=15420
--- Comment #6 from Jan Kara <jack@...e.cz> 2010-03-10 12:25:21 ---
> http://bugzilla.kernel.org/show_bug.cgi?id=15420
>
>
> Theodore Tso <tytso@....edu> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |tytso@....edu
>
>
>
>
> --- Comment #5 from Theodore Tso <tytso@....edu> 2010-03-10 03:12:30 ---
> 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.
Since bugzilla seems to be down now, I'll reply by email:
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...
So something like the patch below?
Honza
--
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists