From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 15420] EXT4_USE_FOR_EXT23 causes wrong free space calculation
on ext2 and ext3
Date: Thu, 11 Mar 2010 16:10:51 GMT
Message-ID: <201003111610.o2BGApXF014076@demeter.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from demeter.kernel.org ([140.211.167.39]:39140 "EHLO
demeter.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S933136Ab0CKQKw (ORCPT
); Thu, 11 Mar 2010 11:10:52 -0500
Received: from demeter.kernel.org (localhost.localdomain [127.0.0.1])
by demeter.kernel.org (8.14.3/8.14.3) with ESMTP id o2BGApkp014079
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for ; Thu, 11 Mar 2010 16:10:51 GMT
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
http://bugzilla.kernel.org/show_bug.cgi?id=15420
--- Comment #16 from Jan Kara 2010-03-11 16:10:46 ---
As for comment #13 - I fully agree with Ted. When admin does "mount -t ext3
...", I think we should give him as close behavior to ext3 as possible by the
principle of the least surprise - and that means nodelalloc. If user wishes
better performance etc, he can always mount the filesystem as ext4 explicitely.
Also I remember some discussions with KDE guys when they were at some point
considering detecting filesystem type and avoid doing fsync if it was ext3 -
hopefully, I convinced them not to do it but I bet someone else had the same
idea and actually implemented it. Not that I'd have too much pity with broken
applications but I prefer to avoid breaking them silently like this...
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.