diff options
| -rw-r--r-- | doc/release-notes/3.5.5.md | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/doc/release-notes/3.5.5.md b/doc/release-notes/3.5.5.md new file mode 100644 index 00000000000..b587688c7d5 --- /dev/null +++ b/doc/release-notes/3.5.5.md @@ -0,0 +1,57 @@ +## Release Notes for GlusterFS 3.5.5 + +This is a bugfix release. The [Release Notes for 3.5.0](3.5.0.md), +[3.5.1](3.5.1.md), [3.5.2](3.5.2.md), [3.5.3](3.5.3.md) and +[3.5.4](3.5.4.md) contain a listing of all the new features that were +added and bugs fixed in the GlusterFS 3.5 stable release. + +### Bugs Fixed: + +- [1166862](https://bugzilla.redhat.com/1166862): rmtab file is a bottleneck when lot of clients are accessing a volume through NFS +- [1217432](https://bugzilla.redhat.com/1217432): DHT:Quota:- brick process crashed after deleting .glusterfs from backend +- [1217433](https://bugzilla.redhat.com/1217433): glusterfsd crashed after directory was removed from the mount point, while self-heal and rebalance were running on the volume +- [1231641](https://bugzilla.redhat.com/1231641): cli crashes when listing quota limits with xml output + +### Known Issues: + +- The following configuration changes are necessary for 'qemu' and 'samba vfs + plugin' integration with libgfapi to work seamlessly: + + 1. `gluster volume set <volname> server.allow-insecure on` + 2. restarting the volume is necessary + + ~~~ + gluster volume stop <volname> + gluster volume start <volname> + ~~~ + + 3. Edit `/etc/glusterfs/glusterd.vol` to contain this line: + + ~~~ + option rpc-auth-allow-insecure on + ~~~ + + 4. restarting glusterd is necessary + + ~~~ + service glusterd restart + ~~~ + + More details are also documented in the Gluster Wiki on the [Libgfapi with qemu libvirt](http://www.gluster.org/community/documentation/index.php/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](http://lists.gnu.org/archive/html/gluster-devel/2014-04/msg00179.html). + The workaround is NOT to call `glfs_fini` for error cases encountered before a successful + `glfs_init`. This is being tracked in [Bug 1134050](https://bugzilla.redhat.com/1134050) for + glusterfs-3.5 and [Bug 1093594](https://bugzilla.redhat.com/1093594) for mainline. + +- If the `/var/run/gluster` directory does not exist enabling quota will likely + fail ([Bug 1117888](https://bugzilla.redhat.com/show_bug.cgi?id=1117888)). + |