On Mon, Apr 11, 2011 at 07:16:06PM -0400, Christoph Hellwig wrote: > On Sun, Apr 10, 2011 at 08:17:58AM -0400, Theodore Tso wrote: > > > > On Apr 8, 2011, at 6:02 PM, Mark Busheman wrote: > > > > > I plan to use data=journal option with ext4. Would like to know if > > > ext4 send FUA (Forced Unit Access) > > > to flush the disk cache? > > > > FUA doesn't cause a cache flush. Ext4 does send cache flush commands, or barriers, to make sure the data written to disk is flushed all the way down to the disk platters on transaction commits. > > Ext4 actually does send FUA requests, just grep for it. With the default > libata config they will be turned into a regular write with a > post-flush, but if you enable the fua module option to the libata module > or use plain SCSI devices the FUA bit (if supported) gets sent all the > way down to the device. Ah, Jens pushed a patch that I hadn't noticed that appears to optionally use FUA for the commit block. Thanks for pointing that out. - Ted -- 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
