SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.5.0.tar.gz
This release is made off jenkins-release-67
-- Gluster Build System
___
Gluster-devel mailing list
Gluster-devel@nongnu.org
Hi,
In QEMU, we initialize gfapi in the following manner:
glfs = glfs_new();
if (!glfs)
goto out;
if (glfs_set_volfile_server() 0)
goto out;
if (glfs_set_logging() 0)
goto out;
if (glfs_init(glfs))
goto out;
...
out:
if (glfs)
glfs_fini(glfs)
On Thu, Apr 17, 2014 at 12:18:17AM -0700, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.5.0.tar.gz
With this release, we have closed all bugs that have all their patches
merged in the release-3.5 branch. In future, we plan to make it more
On 17/04/2014, at 2:36 PM, Niels de Vos wrote:
On Thu, Apr 17, 2014 at 12:18:17AM -0700, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.5.0.tar.gz
With this release, we have closed all bugs that have all their patches
merged in the
On Thu, Apr 17, 2014 at 6:58 PM, Bharata B Rao bharata@gmail.comwrote:
Hi,
In QEMU, we initialize gfapi in the following manner:
glfs = glfs_new();
if (!glfs)
goto out;
if (glfs_set_volfile_server() 0)
goto out;
if (glfs_set_logging() 0)
goto out;
On Thu, Apr 17, 2014 at 12:01:22PM +0200, Niels de Vos wrote:
On Thu, Apr 17, 2014 at 10:23:42AM +0200, Patrick Matthäi wrote:
Hello,
I have got problems building gluster/3.5.0 for Debian:
- First try:
Building as usual (e.g. like 3.4.3) fails because of the missing
Hi,
Given the imminent arrival of the new baby (aka v3.5), it would be a great
point to look at changes or additions to the Getting Started guide.
If you've worked on a feature in 3.5, and think it would be good to add to the
guide, can you please get back to me.
Cheers,
Paul C
No issue with this behaviour - makes sense.
However, the point I made about snapdelete being invoked when thinpool free
space is threatened is a very real issue once you start using snaps. for 3.6
basing snap management on snapshot versions is fine, but I do think this needs
to be extended to
On Thu, Apr 17, 2014 at 7:56 PM, Deepak Shetty dpkshe...@gmail.com wrote:
The glfs_lock indeed seems to work only when glfs_init is succesfull!
We can call glfs_unset_volfile_server for the error case of
glfs_set_volfile_server as a good practice.
But it does look like we need a opposite of
