@Miron Cuperman, in ext3/4 for data=writeback and data=ordered, only meta data is written to the journal. Whereas for the data=journal mode, both data and meta data are written to the journal. So there is more writing to do in the journal mode. Similarly with barriers=1, in order to keep the order of the writes correct, there is a wait performed appropriately. Hence barrier=1, is slower than barriers=0. The fsync performance seems appropriate here. Can you point out to any application specifically, which relies on the fsync() completion time ? (and which is failing currently) ?
** Changed in: linux (Ubuntu) Importance: Medium => Low -- ext3/4 fsyncdata does not flush disk cache https://bugs.launchpad.net/bugs/504632 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
