Linked by Thom Holwerda on Tue 31st Mar 2009 15:47 UTC, submitted by Rahul
Fedora Core The Fedora team has announced the Fedora 11 beta release. It comes packed with new features, such as Ext4 as the default filesystem, Nouveau driver by default, kernel mode setting on Intel, ATI and Nvidia drivers, many virtualization improvements, IBus input method, GCC 4.4, and much more.
Thread beginning with comment 356158
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Ext4 as default
by Rahul on Tue 31st Mar 2009 23:13 UTC in reply to "RE[6]: Ext4 as default"
Rahul
Member since:
2005-07-06

Newly created files having delayed allocation didn't actually result in zero length files in my tests nor was it the problem originated stated in bug report. My tests were simply to copy a large ISO file and pull the power within 10 seconds and run md5sum on it. It worked out fine. Of course, I might be testing the wrong thing.

Reply Parent Score: 1

RE[8]: Ext4 as default
by sbergman27 on Tue 31st Mar 2009 23:18 in reply to "RE[7]: Ext4 as default"
sbergman27 Member since:
2005-07-24

My tests were simply to copy a large ISO file and pull the power within 10 seconds and run md5sum on it. It worked out fine.

Well, if it can really do that, while maintaining the bulk of the speed increases, and fragmentation avoidance advantages, of delayed allocation, then I am delighted. But if that is the case, why does Ted imply that it would not be?

To my knowledge, you are not "testing the wrong thing". That is exactly where I would expect to observe the problem.

Edited 2009-03-31 23:20 UTC

Reply Parent Score: 2

RE[9]: Ext4 as default
by Rahul on Tue 31st Mar 2009 23:30 in reply to "RE[8]: Ext4 as default"
Rahul Member since:
2005-07-06

My understanding is that Ted is talking about a slightly different case where a large number of new files are being created simultaneously as in say a desktop environment creating its new settings on a new user and NOT closing the files while I am actually testing a single large write and since the write is not starved for resources (aka multiple files trying to get disk access), it will be committed as soon as close is called (even without fsync) since the Rawhide already has that patch.

http://cvs.fedoraproject.org/viewvc/rpms/kernel/devel/linux-2.6-ext...

At this point, this debate is rather silly since it seems most people participating in it haven't actually tested it yet and I rather hear from people actually testing this thing and providing feedback on actual problems.

Reply Parent Score: 1