[Gluster-users] Monthly GlusterFS 3.5 release, fixing two bugs

Niels de Vos ndevos at redhat.com
Mon Sep 21 15:07:18 UTC 2015

[original post at http://blog.nixpanic.net/2015/09/monthly-glusterfs-35-release-fixing-two.html]

Hi all,

last week an other release of the stable glusterfs-3.5 branch was made.
Packages for most distributions are ready now, enjoy!

Note that the 3.5 version will become End-Of-Life when glusterfs-3.8 is
ready. We keep updating and releasing new minor versions for the three
last releases of Gluster, currently 3.7, 3.6 and 3.5. The current
planning for 3.8 is scheduled for the end of this year, so start
thinking about an upgrade to a newer version if you are still using 3.5.

Packages for Fedora 21 are available in updates-testing, RPMs and .debs
can be found on the main Gluster download site.

This is a bugfix release. The Release Notes for 3.5.0, 3.5.1, 3.5.2,
3.5.3, 3.5.4 and 3.5.5 contain a listing of all the new features that
were added and bugs fixed in the GlusterFS 3.5 stable release.

Bugs Fixed:

    1244118: unix domain sockets on Gluster/NFS are created as fifo/pipe
    1244147: Many build warnings when compiling glusterfs-3.5 with recent gcc

Known Issues:

    The following configuration changes are necessary for 'qemu' and
    'samba vfs plugin' integration with libgfapi to work seamlessly:

        gluster volume set <volname> server.allow-insecure on
        restarting the volume is necessary

         gluster volume stop <volname>
         gluster volume start <volname>

        Edit /etc/glusterfs/glusterd.vol to contain this line:

         option rpc-auth-allow-insecure on

        restarting glusterd is necessary

         service glusterd restart

	More details are also documented in the Gluster Wiki on the
        Libgfapi with qemu libvirt page.

    For Block Device translator based volumes open-behind translator at
    the client side needs to be disabled.

    gluster volume set <volname> performance.open-behind disabled

    libgfapi clients calling glfs_fini before a successful glfs_init
    will cause the client to hang as reported here. The workaround is
    NOT to call glfs_fini for error cases encountered before a
    successful glfs_init. This is being tracked in Bug 1134050 for
    glusterfs-3.5 and Bug 1093594 for mainline.

    If the /var/run/gluster directory does not exist enabling quota will
    likely fail (Bug 1117888).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150921/e0687cb1/attachment.sig>

More information about the Gluster-users mailing list