Description of problem: There are a bunch of posix compliance tests that fail because of sharding translator not appropriately handling fops on symlinks. This BZ is to be associated with all the patches sent to fix these issues. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/10995 (features/shard: Handle symlinks appropriately in fops) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10995 (features/shard: Handle symlinks appropriately in fops) posted (#2) for review on master by Niels de Vos (ndevos)
REVIEW: http://review.gluster.org/10995 (features/shard: Handle symlinks appropriately in fops) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11065 (features/shard: Skip shards resolution if lookup on /.shard returns ENOENT) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/10995 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 990cb828a2e9b0d83a767977712305534fac39e2 Author: Krutika Dhananjay <kdhananj> Date: Thu May 21 14:58:26 2015 +0530 features/shard: Handle symlinks appropriately in fops (f)stat, unlink and rename must skip doing inode_ctx_get() of shard block size on symbolic links. Change-Id: I68688532164dd2ab491ff5c59b343174f8c4ce7f BUG: 1223759 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/10995 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
REVIEW: http://review.gluster.org/11065 (features/shard: Skip shards resolution if lookup on /.shard returns ENOENT) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11065 (features/shard: Skip shards resolution if lookup on /.shard returns ENOENT) posted (#4) for review on master by Krutika Dhananjay (kdhananj)
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.8.0, please open a new bug report. glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user