Re: [PATCH 2/5] ext3: call blkdev_issue_flush on fsync()

Jeff Garzik
2009-03-30T01:52:16Z

Fernando Luis Vázquez Cao wrote:
> To ensure that bits are truly on-disk after an fsync or fdatasync, we
> should force a disk flush explicitly when there is dirty data/metadata
> and the journal didn't emit a write barrier (either because metadata is
> not being synched or barriers are disabled).
>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>

Your patches do not seem to propagate the issue-flush error code, even
when it is easily available.

Jeff