From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.6 v3 0/3] Bug fixes for gluster
Date: Tue, 19 Apr 2016 11:48:17 -0400 [thread overview]
Message-ID: <20160419154817.GD7187@localhost.localdomain> (raw)
In-Reply-To: <cover.1461075204.git.jcody@redhat.com>
On Tue, Apr 19, 2016 at 10:16:18AM -0400, Jeff Cody wrote:
> Change from v2:
>
> Look at the error return from the aio callback from
> fsync, as well. (thanks Kevin)
>
>
> Bug fixes for gluster; third patch is to prevent
> a potential data loss when trying to recover from
> a recoverable error (such as ENOSPC).
>
> The final patch closes the gluster fd and sets the
> protocol drv to NULL on fsync failure in gluster;
> we have no way of knowing what gluster versions
> support retaining fysnc cache on error, so until
> we do the safest thing to do is invalidate the
> drive.
>
> Jeff Cody (3):
> block/gluster: return correct error value
> block/gluster: code movement of qemu_gluster_close()
> block/gluster: prevent data loss after i/o error
>
> block/gluster.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++----------
> configure | 8 ++++++
> 2 files changed, 72 insertions(+), 13 deletions(-)
>
> --
> 1.9.3
>
Thanks,
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc.git block
-Jeff
prev parent reply other threads:[~2016-04-19 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:16 [Qemu-devel] [PATCH for-2.6 v3 0/3] Bug fixes for gluster Jeff Cody
2016-04-19 14:16 ` [Qemu-devel] [PATCH for-2.6 v3 1/3] block/gluster: return correct error value Jeff Cody
2016-04-19 14:16 ` [Qemu-devel] [PATCH for-2.6 v3 2/3] block/gluster: code movement of qemu_gluster_close() Jeff Cody
2016-04-19 14:16 ` [Qemu-devel] [PATCH for-2.6 v3 3/3] block/gluster: prevent data loss after i/o error Jeff Cody
2016-04-19 15:48 ` Jeff Cody [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160419154817.GD7187@localhost.localdomain \
--to=jcody@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).