Revision a27a263bae072a499acc77b632238a6dacccf888 authored by Christoph Hellwig on 16 June 2011, 12:02:23 UTC, committed by Alex Elder on 16 June 2011, 15:52:39 UTC
There's no reason not to support cache flushing on external log devices. The only thing this really requires is flushing the data device first both in fsync and log commits. A side effect is that we also have to remove the barrier write test during mount, which has been superflous since the new FLUSH+FUA code anyway. Also use the chance to flush the RT subvolume write cache before the fsync commit, which is required for correct semantics. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
1 parent c46a131
Computing file changes ...
