[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110411231606.GA9406@infradead.org>
Date: Mon, 11 Apr 2011 19:16:06 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Theodore Tso <tytso@....EDU>
Cc: Mark Busheman <markbusheman@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: Does ext4 send FUA to flush disk cache
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.
The same also applies to btrfs, gfs2, nilfs2, xfs and if you enable the
non-default config ext3 and reiserfs. Note that all the filesystem also
do regular flushes as pre-flushes during the journal commit or
equivalent and as part of the fsync implementation.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists