The first beta for GlusterFS 3.5.3 is now available for download.
Packages for different distributions will land on the download server over the next few days. When packages become available, the package maintainers will send a notification to the gluster-users mailinglist.
With this beta release, we make it possible for bug reporters and testers to check if issues have indeed been fixed. All community members are invited to test and/or comment on this release.
If a bug from the list below has not been sufficiently fixed, please open the bug report, leave a comment with details of the testing and change the status of the bug to ASSIGNED.
In case someone has successfully verified a fix for a bug, please change the status of the bug to VERIFIED.
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.vol
to 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_fini
before a successfull 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 successfull glfs_init
. This is being tracked in Bug 1134050 for glusterfs-3.5 and Bug 1093594 for mainline. /var/run/gluster
directory 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...