Gluster blog stories provide high-level spotlights on our users all over the world
Even though GlusterFS 3.6.0 has been released last week, the 3.5 stable series continues to live on! The 2nd beta for GlusterFS 3.5.3 is now available for testing. Many bugs have been fixed since the 3.5.2 release, check the references below for details.
Bug reporters are encouraged to verify the fixes, and we invite others to test this beta to check if there are no regressions. Please see the announcement email for further information. When the release proves to be stable, a final 3.5.3 will be made available in a week or so.
Packages for different distributions can be found on the main download server.
This is a bugfix release. The Release Notes for 3.5.0, 3.5.1 and 3.5.2 contain a listing of all the new features that were added and bugs fixed in the GlusterFS 3.5 stable release.
gluster volume set <volname> server.allow-insecure on
gluster volume stop <volname>
gluster volume start <volname>
/etc/glusterfs/glusterd.volto contain this line:
option rpc-auth-allow-insecure on
service glusterd restart
More details are also documented in the Gluster Wiki on the Libgfapi with qemu libvirt page.
gluster volume set <volname> performance.open-behind disabled
glfs_finibefore a successfull
glfs_initwill cause the client to hang as reported here. The workaround is NOT to call
glfs_finifor error cases encountered before a successfull
glfs_init. This is being tracked in Bug 1134050 for glusterfs-3.5 and Bug 1093594 for mainline.
/var/run/glusterdirectory does not exist enabling quota will likely fail (Bug 1117888).
2020 has not been a year we would have been able to predict. With a worldwide pandemic and lives thrown out of gear, as we head into 2021, we are thankful that our community and project continued to receive new developers, users and make small gains. For that and a...
It has been a while since we provided an update to the Gluster community. Across the world various nations, states and localities have put together sets of guidelines around shelter-in-place and quarantine. We request our community members to stay safe, to care for their loved ones, to continue to be...
The initial rounds of conversation around the planning of content for release 8 has helped the project identify one key thing – the need to stagger out features and enhancements over multiple releases. Thus, while release 8 is unlikely to be feature heavy as previous releases, it will be the...