Re: ext2 + -osync: not as easy as it seems

[Theodore Tso]

On Wed, Jan 14, 2009 at 03:08:04PM +0100, Jens Axboe wrote:
> 
> It also guarentees that when you get a completion for that barrier
> write, it's on safe storage. Think of it as a flush-write-flush
> operation, in the presence of write back caching.
> 

Is that true even if the barrier isn't attached to a write operation,
i.e., when using

      blkdev_issue_flush(sb, NULL);

?

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/