Description of problem: In a sharded volume, unlink of files with holes fails with ENOENT. This is because shard_common_lookup_shards() treats absence of participant shards as failure. But in case of files with holes, it is possible for most shards to not exist. And shard translator must not fail unlinks and renames (where the dst exists && is sharded && has holes). 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/11737 (features/shard: Handle unlink of files with holes appropriately in unlink() and rename()) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11737 (features/shard: Handle unlink of files with holes appropriately in unlink() and rename().) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11737 (features/shard: Handle unlink of files with holes appropriately in unlink() and rename()) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11737 (features/shard: Handle unlink of files with holes appropriately in unlink() and rename().) posted (#4) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/11737 (features/shard: Handle unlink of files with holes appropriately in unlink() and rename().) posted (#5) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/11737 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 385acc675c512c63f7051d46ad96666ea34cf0b5 Author: Krutika Dhananjay <kdhananj> Date: Wed Jul 22 15:18:20 2015 +0530 features/shard: Handle unlink of files with holes appropriately in unlink() and rename(). Change-Id: I25a02386dc95580c2e76a13fdd8e11a0df234d56 BUG: 1245547 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/11737 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: NetBSD Build System <jenkins.org>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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