REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#3) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#4) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#5) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#6) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#7) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#8) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#9) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#10) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#11) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#12) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#13) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#14) for review on master by susant palai (spalai)
REVIEW: http://review.gluster.org/7599 (DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume).) posted (#15) for review on master by Raghavendra G (rgowdapp)
COMMIT: http://review.gluster.org/7599 committed in master by Vijay Bellur (vbellur) ------ commit b8f3aab95f01ac7d590a5ba490e890d9cf8c2e50 Author: Susant Palai <spalai> Date: Tue May 13 12:56:17 2014 -0400 DHT/readdirp: Directory not shown/healed on mount point if exists on single brick(non first up subvolume). Problem: If snapshot is taken, when mkdir has succeeded only on hashed_subvolume, then after restoring snapshot the directory is not shown on mount point. Why: dht_readdirp takes only those directory entries in to account, which are present on first_up_subvolume. Hence, if the "hashed subvolume" is not same as first_up_subvolume, it wont be listed on mount point and also not healed. Solution: Case 1: (Rebalance not running)If hashed subvolume is NULL or down then filter in first_up_subvolume. Other wise the corresponding hashed subvolume will take care of the directory entry. Case 2: If readdirp_optimize option is turned on then read from first_up_subvol Change-Id: Idaad28f1c9f688dbfb1a8a3ab8b244510c02365e BUG: 1092433 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/7599 Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users