diff options
authorNiels de Vos <>2016-11-23 15:27:59 +0100
committerNiels de Vos <>2016-11-23 07:20:13 -0800
commitc485ea191de824102adb5cd092bd75931f65de2c (patch)
parent8cd077a05f5504a0e94a3565ce815bc4cec9972c (diff)
doc: release-notes for GlusterFS-3.8.6v3.8.6
Change-Id: I8cc3631497303bc7ccb2a0d77c3e25dedb3a3836 BUG: 1384412 Signed-off-by: Niels de Vos <> Reviewed-on: CentOS-regression: Gluster Build System <> NetBSD-regression: NetBSD Build System <> Smoke: Gluster Build System <>
1 files changed, 60 insertions, 0 deletions
diff --git a/doc/release-notes/ b/doc/release-notes/
new file mode 100644
index 00000000000..1ad77f3dbf8
--- /dev/null
+++ b/doc/release-notes/
@@ -0,0 +1,60 @@
+# Release notes for Gluster 3.8.6
+This is a bugfix release. The [Release Notes for 3.8.0](,
+[3.8.1](, [3.8.2](, [3.8.3](, [3.8.4]( and
+[3.8.5]( contain a listing of all the new features that were added and
+bugs fixed in the GlusterFS 3.8 stable release.
+## Change in port allocation, may affect deployments with strict firewalls
+'''Problem description''': GlusterD used to assume that the brick port which
+was previously allocated to a brick, would still be available, and in doing so
+would reuse the port for the brick without registering with the port map
+server. The port map server would not be aware of the brick reusing the same
+port, and try to allocate it to another process, and in turn result in that
+process' failure to connect to the port.
+'''Fix and port usage changes''': With the fix, we force GlusterD to unregister
+a port previously used by the brick, and register a new port with the port map
+server and then use it. As a result of this change, there will be no conflict
+between processes competing over the same port, thereby fixing the issue. Also
+because of this change, a brick process on restart is not guaranteed to reuse
+the same port it used to be connected to.
+## Bugs addressed
+A total of 34 patches have been merged, addressing 31 bugs:
+- [#1336376]( Sequential volume start&stop is failing with SSL enabled setup.
+- [#1347717]( removal of file from nfs mount crashs ganesha server
+- [#1369766]( glusterd: add brick command should re-use the port for listening which is freed by remove-brick.
+- [#1371397]( [Disperse] dd + rm + ls lead to IO hang
+- [#1375125]( arbiter volume write performance is bad.
+- [#1377448]( glusterd: Display proper error message and fail the command if hook script is not present during gluster volume set all cluster.enable-shared-storage <enable/disable> command
+- [#1384345]( usage text is wrong for use-readdirp mount default
+- [#1384356]( Polling failure errors getting when volume is started&stopped with SSL enabled setup.
+- [#1385442]( invalid argument warning messages seen in fuse client logs 2016-09-30 06:34:58.938667] W [dict.c:418ict_set] (-->/usr/lib64/glusterfs/3.8.4/xlator/cluster/ 0-dict: !this || !value for key=link-count [Invalid argument]
+- [#1385620]( Recording (ffmpeg) processes on FUSE get hung
+- [#1386071]( Spurious permission denied problems observed
+- [#1387976]( Continuous warning messages getting when one of the cluster node is down on SSL setup.
+- [#1388354]( Memory Leaks in snapshot code path
+- [#1388580]( crypt: changes needed for openssl-1.1 (coming in Fedora 26)
+- [#1388948]( glusterfs can't self heal character dev file for invalid dev_t parameters
+- [#1390838]( write-behind: flush stuck by former failed write
+- [#1390870]( DHT: Rebalance- Misleading log messages from __dht_check_free_space function
+- [#1391450]( md-cache: Invalidate cache entry in case of OPEN with O_TRUNC
+- [#1392288]( gfapi clients crash while using async calls due to double fd_unref
+- [#1392364]( trashcan max file limit cannot go beyond 1GB
+- [#1392716]( Quota version not changing in the quota.conf after upgrading to 3.7.1 from 3.6.1
+- [#1392846]( Hosted Engine VM paused post replace-brick operation
+- [#1392868]( The FUSE client log is filling up with posix_acl_default and posix_acl_access messages
+- [#1393630]( Better logging when reporting failures of the kind "<file-path> Failing MKNOD as quorum is not met"
+- [#1393682]( stat of file is hung with possible deadlock
+- [#1394108]( Continuous errors getting in the mount log when the volume mount server glusterd is down.
+- [#1394187]( SMB[md-cache Private Build]:Error messages in brick logs related to upcall_cache_invalidate gf_uuid_is_null
+- [#1394226]( "nfs-grace-monitor" timed out messages observed
+- [#1394883]( Failed to enable nfs-ganesha after disabling nfs-ganesha cluster
+- [#1395627]( Labelled geo-rep checkpoints hide geo-replication status
+- [#1396418]( [md-cache]: All bricks crashed while performing symlink and rename from client at the same time