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: Thu, 11 Mar 2010 16:17:02 GMT [thread overview]
Message-ID: <201003111617.o2BGH2ts015927@demeter.kernel.org> (raw)
In-Reply-To: <bug-15420-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15420
--- Comment #17 from Eric Sandeen <sandeen@redhat.com> 2010-03-11 16:16:46 ---
(In reply to comment #16)
> 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.
Under what circumstances, then, do we recommend mounting ext3 with the ext4
driver?
The user will get different allocation behavior as well; will that also be a
surprise?
I just want to be clear in our recommendations about this stuff...
> 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...
I think by having this config option at -all- we have really muddied the
waters, to be honest ... but I suppose this is all better hashed outon the
list, not in this bug. :)
--
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 prev parent reply other threads:[~2010-03-11 16:17 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
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 [this message]
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=201003111617.o2BGH2ts015927@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).