## Release Notes for GlusterFS 3.5.2

This is mostly a bugfix release. The [Release Notes for 3.5.0](./3.5.0.md) and [3.5.1](./3.5.1.md) contain a listing of all the new features that were added and bugs fixed.

### Bugs Fixed:

- [1096020](https://bugzilla.redhat.com/1096020): NFS server crashes in _socket_read_vectored_request
- [1100050](https://bugzilla.redhat.com/1100050): Can't write to quota enable folder
- [1103050](https://bugzilla.redhat.com/1103050): nfs: reset command does not alter the result for nfs options earlier set
- [1105891](https://bugzilla.redhat.com/1105891): features/gfid-access: stat on .gfid virtual directory return EINVAL
- [1111454](https://bugzilla.redhat.com/1111454): creating symlinks generates errors on stripe volume
- [1112111](https://bugzilla.redhat.com/1112111): Self-heal errors with "afr crawl failed for child 0 with  ret -1" while performing rolling upgrade.
- [1112348](https://bugzilla.redhat.com/1112348): [AFR] I/O fails when one of the replica nodes go down
- [1112659](https://bugzilla.redhat.com/1112659): Fix inode leaks in gfid-access xlator
- [1112980](https://bugzilla.redhat.com/1112980): NFS subdir authentication doesn't correctly handle multi-(homed,protocol,etc) network addresses
- [1113007](https://bugzilla.redhat.com/1113007): nfs-utils should be installed as dependency while installing glusterfs-server
- [1113403](https://bugzilla.redhat.com/1113403): Excessive logging in quotad.log of the kind 'null client'
- [1113749](https://bugzilla.redhat.com/1113749): client_t clienttable cliententries are never expanded when all entries are used
- [1113894](https://bugzilla.redhat.com/1113894): AFR : self-heal of few files not happening when a AWS EC2 Instance is back online after a restart
- [1113959](https://bugzilla.redhat.com/1113959): Spec %post server does not wait for the old glusterd to exit
- [1114501](https://bugzilla.redhat.com/1114501): Dist-geo-rep : deletion of files on master,  geo-rep fails to propagate to slaves.
- [1115369](https://bugzilla.redhat.com/1115369): Allow the usage of the wildcard character '*' to the options "nfs.rpc-auth-allow" and "nfs.rpc-auth-reject"
- [1115950](https://bugzilla.redhat.com/1115950): glfsheal: Improve the way in which we check the presence of replica volumes
- [1116672](https://bugzilla.redhat.com/1116672): Resource cleanup doesn't happen for clients on servers after disconnect
- [1116997](https://bugzilla.redhat.com/1116997): mounting a volume over NFS (TCP) with MOUNT over UDP fails
- [1117241](https://bugzilla.redhat.com/1117241): backport 'gluster volume status --xml' issues
- [1120151](https://bugzilla.redhat.com/1120151): Glustershd memory usage too high
- [1124728](https://bugzilla.redhat.com/1124728): SMB: CIFS mount fails with the latest glusterfs rpm's

### 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](../Feature Planning/GlusterFS 3.5/libgfapi with qemu libvirt.md) 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 successfull `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 successfull
  `glfs_init`.

- 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)).
