## Release Notes for GlusterFS 3.5.4 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) and [3.5.3](3.5.3.md) contain a listing of all the new features that were added and bugs fixed in the GlusterFS 3.5 stable release. ### Bugs Fixed: - [1092037](https://bugzilla.redhat.com/1092037): Issues reported by Cppcheck static analysis tool - [1101138](https://bugzilla.redhat.com/1101138): meta-data split-brain prevents entry/data self-heal of dir/file respectively - [1115197](https://bugzilla.redhat.com/1115197): Directory quota does not apply on it's sub-directories - [1159968](https://bugzilla.redhat.com/1159968): glusterfs.spec.in: deprecate *.logrotate files in dist-git in favor of the upstream logrotate files - [1160711](https://bugzilla.redhat.com/1160711): libgfapi: use versioned symbols in libgfapi.so for compatibility - [1161102](https://bugzilla.redhat.com/1161102): self heal info logs are filled up with messages reporting split-brain - [1162150](https://bugzilla.redhat.com/1162150): AFR gives EROFS when fop fails on all subvolumes when client-quorum is enabled - [1162226](https://bugzilla.redhat.com/1162226): bulk remove xattr should not fail if removexattr fails with ENOATTR/ENODATA - [1162230](https://bugzilla.redhat.com/1162230): quota xattrs are exposed in lookup and getxattr - [1162767](https://bugzilla.redhat.com/1162767): DHT: Rebalance- Rebalance process crash after remove-brick - [1166275](https://bugzilla.redhat.com/1166275): Directory fd leaks in index translator - [1168173](https://bugzilla.redhat.com/1168173): Regression tests fail in quota-anon-fs-nfs.t - [1173515](https://bugzilla.redhat.com/1173515): [HC] - mount.glusterfs fails to check return of mount command. - [1174250](https://bugzilla.redhat.com/1174250): Glusterfs outputs a lot of warnings and errors when quota is enabled - [1177339](https://bugzilla.redhat.com/1177339): entry self-heal in 3.5 and 3.6 are not compatible - [1177928](https://bugzilla.redhat.com/1177928): Directories not visible anymore after add-brick, new brick dirs not part of old bricks - [1184528](https://bugzilla.redhat.com/1184528): Some newly created folders have root ownership although created by unprivileged user - [1186121](https://bugzilla.redhat.com/1186121): tar on a gluster directory gives message "file changed as we read it" even though no updates to file in progress - [1190633](https://bugzilla.redhat.com/1190633): self-heal-algorithm with option "full" doesn't heal sparse files correctly - [1191006](https://bugzilla.redhat.com/1191006): Building argp-standalone breaks nightly builds on Fedora Rawhide - [1192832](https://bugzilla.redhat.com/1192832): log files get flooded when removexattr() can't find a specified key or value - [1200764](https://bugzilla.redhat.com/1200764): [AFR] Core dump and crash observed during disk replacement case - [1202675](https://bugzilla.redhat.com/1202675): Perf: readdirp in replicated volumes causes performance degrade - [1211841](https://bugzilla.redhat.com/1211841): glusterfs-api.pc versioning breaks QEMU - [1222150](https://bugzilla.redhat.com/1222150): readdirp return 64bits inodes even if enable-ino32 is set ### Known Issues: - The following configuration changes are necessary for 'qemu' and 'samba vfs plugin' integration with libgfapi to work seamlessly: 1. `gluster volume set server.allow-insecure on` 2. restarting the volume is necessary ~~~ gluster volume stop gluster volume start ~~~ 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 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)).