REVIEW: http://review.gluster.org/12706 (cluster/tier: readdirp to cold tier only) posted (#1) for review on release-3.7 by N Balachandran (nbalacha)
REVIEW: http://review.gluster.org/12722 (cluster/tier: readdirp to cold tier only) posted (#1) for review on release-3.7 by Dan Lambright (dlambrig)
REVIEW: http://review.gluster.org/12722 (cluster/tier: readdirp to cold tier only) posted (#2) for review on release-3.7 by Dan Lambright (dlambrig)
COMMIT: http://review.gluster.org/12722 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit b8c56ebe617327d570c252f8c411c85a84e727e6 Author: Dan Lambright <dlambrig> Date: Wed Nov 4 15:33:22 2015 -0500 cluster/tier: readdirp to cold tier only It is possible a file would get migrated in the middle of a readdir operation. If there are four subvolumes A,B,C,D, and if readdir reads them in order and reaches subvol B, then, if a file is moved from D to A, it will not be included in the readdir output. This phenonema has pre-existed in DHT migration but is more apparent in tiering. When a file is moved off the hashed subvolume a T file is created. For tiering, we will make the cold subvolume the hashed subvolume. This will ensure the creation of a T file. Readdir will not skip T files in the tier translator. Making the cold subvolume the hashed subvolume ensures the T files created on promotions or creates will be less likely to fill the volume. Creates still put the data on the hot subvolume. This is a backport of 12530 > Change-Id: Ifde557d3d0e94a4570ca9f115adee3db2ee75407 > BUG: 1281598 > Signed-off-by: Dan Lambright <dlambrig> > Reviewed-on: http://review.gluster.org/12530 > Tested-by: Gluster Build System <jenkins.com> > Tested-by: NetBSD Build System <jenkins.org> > Reviewed-by: N Balachandran <nbalacha> > Reviewed-by: Raghavendra G <rgowdapp> Signed-off-by: Dan Lambright <dlambrig> Signed-off-by: Dan Lambright <dlambrig> Conflicts: xlators/cluster/dht/src/tier.c Change-Id: I5720a4cd04ae5088e5d7d23439b0f90d6bbc6265 BUG: 1283923 Reviewed-on: http://review.gluster.org/12722 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: N Balachandran <nbalacha> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.7, please open a new bug report. glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user