From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, rwheeler@redhat.com,
pkarampu@redhat.com, rgowdapp@redhat.com, ndevos@redhat.com
Subject: [Qemu-devel] [PATCH for-2.6 v2 0/3] Bug fixes for gluster
Date: Tue, 19 Apr 2016 08:07:27 -0400 [thread overview]
Message-ID: <cover.1461067248.git.jcody@redhat.com> (raw)
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 | 66 ++++++++++++++++++++++++++++++++++++++++++++++-----------
configure | 8 +++++++
2 files changed, 62 insertions(+), 12 deletions(-)
--
1.9.3
next reply other threads:[~2016-04-19 12:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 12:07 Jeff Cody [this message]
2016-04-19 12:07 ` [Qemu-devel] [PATCH for-2.6 v2 1/3] block/gluster: return correct error value Jeff Cody
2016-04-19 12:07 ` [Qemu-devel] [PATCH for-2.6 v2 2/3] block/gluster: code movement of qemu_gluster_close() Jeff Cody
2016-04-19 12:07 ` [Qemu-devel] [PATCH for-2.6 v2 3/3] block/gluster: prevent data loss after i/o error Jeff Cody
2016-04-19 12:27 ` Kevin Wolf
2016-04-19 12:29 ` Jeff Cody
2016-04-19 12:18 ` [Qemu-devel] [PATCH for-2.6 v2 0/3] Bug fixes for gluster Ric Wheeler
2016-04-19 14:09 ` Jeff Cody
2016-04-20 1:56 ` Ric Wheeler
2016-04-20 9:24 ` Kevin Wolf
2016-04-20 10:40 ` Ric Wheeler
2016-04-20 11:46 ` Kevin Wolf
2016-04-20 18:38 ` Rik van Riel
2016-04-21 8:43 ` Kevin Wolf
2016-04-20 18:37 ` Rik van Riel
2016-04-20 5:15 ` Raghavendra Gowdappa
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=cover.1461067248.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=ndevos@redhat.com \
--cc=pkarampu@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rgowdapp@redhat.com \
--cc=rwheeler@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.