Closing according to comment #7.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308542
Title:
hang in qemu_gluster_init
Status in QEMU:
Fi
Verified that this fixes the hang and no change is required in gluster
driver of QEMU after this fix in glusterfs code.
On Mon, Jun 23, 2014 at 11:59 PM, nixpanic wrote:
> A complete fix has been included in the glusterfs master-branch. It has
> not (yet) been requested or marked for backportin
A complete fix has been included in the glusterfs master-branch. It has
not (yet) been requested or marked for backporting to a stable (3.5.x)
branch.
* https://bugzilla.redhat.com/1091335 with
http://review.gluster.org/7857
The issue with glfs_set_logging is fixed in the almost released
glusterf
Also I should add a note to this related bug I filed against gluster -
https://bugzilla.redhat.com/show_bug.cgi?id=1088589
This bug is what causes the glfs_set_logging call to fail, and fall into
the hang case.
** Bug watch added: Red Hat Bugzilla #1088589
https://bugzilla.redhat.com/show_bug.
On Fri, Apr 18, 2014 at 02:38:57PM -, Soumya Koduri wrote:
> " glfs_init" cannot be called before since it checks for
> cmds_args->volfile_server which is allocated only in
> "glfs_set_volfile_server". We should either modify "glfs_fini" or
Soumya - Thanks for offering to fix this in gluster
" glfs_init" cannot be called before since it checks for
cmds_args->volfile_server which is allocated only in
"glfs_set_volfile_server". We should either modify "glfs_fini" or
define a new function to do the cleanup based on if init is done or not.
--
You received this bug notification because
