file-posix: Make bdrv_flush() failure permanent without O_DIRECT
commite5bcf967fb80ff9cf4d0c0d643e985ec5ff94e91
authorKevin Wolf <kwolf@redhat.com>
Wed, 22 Mar 2017 21:00:05 +0000 (22 22:00 +0100)
committerMax Reitz <mreitz@redhat.com>
Mon, 27 Mar 2017 14:53:42 +0000 (27 16:53 +0200)
tree8c4ebc20c2a2a3a646822f0742e7c1944b1734bb
parenta12a712a7dfbd2e2f4882ef2c90a9b2162166dd7
file-posix: Make bdrv_flush() failure permanent without O_DIRECT

Success for bdrv_flush() means that all previously written data is safe
on disk. For fdatasync(), the best semantics we can hope for on Linux
(without O_DIRECT) is that all data that was written since the last call
was successfully written back. Therefore, and because we can't redo all
writes after a flush failure, we have to give up after a single
fdatasync() failure. After this failure, we would never be able to make
the promise that a successful bdrv_flush() makes.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-id: 20170322210005.16533-1-kwolf@redhat.com
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
block/file-posix.c