[Bug 15420] EXT4_USE_FOR_EXT23 causes wrong free space calculation on ext2 and ext3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



http://bugzilla.kernel.org/show_bug.cgi?id=15420





--- Comment #16 from Jan Kara <jack@xxxxxxx>  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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux