diff options
| author | Jeff Cody <jcody@redhat.com> | 2016-04-05 10:40:09 -0400 |
|---|---|---|
| committer | Timothy Pearson <tpearson@raptorengineering.com> | 2019-11-29 20:03:49 -0600 |
| commit | 8ea3d1327ba111398c7b5fa3c3583d090004d6b2 (patch) | |
| tree | 531ba8e6cb19c5515a0d4679d0b1d2a6336a73ad /trace | |
| parent | 06b7d14761e6ef666d061ad42bcd2e1167313061 (diff) | |
| download | hqemu-8ea3d1327ba111398c7b5fa3c3583d090004d6b2.zip hqemu-8ea3d1327ba111398c7b5fa3c3583d090004d6b2.tar.gz | |
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 'trace')
0 files changed, 0 insertions, 0 deletions
