aboutsummaryrefslogtreecommitdiff
path: root/xen-common.c
diff options
context:
space:
mode:
authorJeff Cody <jcody@redhat.com>2016-04-05 10:40:09 -0400
committerJeff Cody <jcody@redhat.com>2016-04-19 12:24:59 -0400
commitd85fa9eb87ba736d2d5ce342fc35f507c8fe29f2 (patch)
treeb5526240fd70adc449d032a58edd035c4abc2c3e /xen-common.c
parent5d4343e6c2682fb7fe66f1560d1823b5a26e7b2f (diff)
block/gluster: prevent data loss after i/o error
Upon receiving an I/O error after an fsync, by default gluster will dump its cache. However, QEMU will retry the fsync, which is especially useful when encountering errors such as ENOSPC when using the werror=stop option. When using caching with gluster, however, the last written data will be lost upon encountering ENOSPC. Using the write-behind-cache xlator option of 'resync-failed-syncs-after-fsync' should cause gluster to retain the cached data after a failed fsync, so that ENOSPC and other transient errors are recoverable. Unfortunately, we have no way of knowing if the 'resync-failed-syncs-after-fsync' xlator option is supported, so for now close the fd and set the BDS driver to NULL upon fsync error. Signed-off-by: Jeff Cody <jcody@redhat.com>
Diffstat (limited to 'xen-common.c')
0 files changed, 0 insertions, 0 deletions