> >> (except for ext3, where, for data integrity with a volatile writeback > >> cache, defaults + barriers=1, since that safe default was never accepted > >> upstream) > > > > Why isn't it the Fedora default? > > Excellent question - we probably should flip it over in fedora to the safe > default. > > Historically, there were times that applications got fsync happy (like > firefox) and basically stopped working when barriers were enabled (only > because they were waiting for the fsync to actually do something). > > I believe that we have exposed most of this kind of thing by now after > years of default ext4 use so this should be mostly resolved, weren't barriers kicked out with kernel 2.6.37? see http://kernelnewbies.org/Linux_2_6_37#head-9d59a04087857adeda842dd4ed97f00abd824e23 and http://lwn.net/Articles/400541/ Kind regards, Gerd -- Address (better: trap) for people I really don't want to get mail from: jonas@xxxxxxxxxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
