Description of problem: This is a bug that is to be associated with the ongoing efforts w.r.t sharding translator. https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20 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/9841 (WIP: Sharding xlator) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#4) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9841 (features/shard: Introducing sharding translator) posted (#5) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9841 (features/shard: Introducing sharding translator) posted (#6) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/9841 committed in master by Vijay Bellur (vbellur) ------ commit 6f389fbb812b384bdd9bf4a20e86930505531996 Author: Krutika Dhananjay <kdhananj> Date: Fri Nov 21 11:47:23 2014 +0530 features/shard: Introducing sharding translator Based on the high-level design by Anand V. Avati which can be found @ https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20 Still to-do: * complete implementation of inode write fops - [f]truncate, zerofill, fallocate, discard * introduce transaction mechanism in inode write fops * complete readv * Handle open with O_TRUNC * Handle unlinking of all shards during unlink/rename * Compute total ia_size and ia_blocks in lookup, readdirp, etc * wind fsync/flush on all shards Note: Most of the items above are related. Once we come up with a clean way to determine the last shard/shard count for a file/file size and the mgmt of sparse regions of the file, implementing them becomes trivial. Change-Id: Id871379b53a4a916e4baa2e06f197dd8c0043b0f BUG: 1200082 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/9841 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10537 (doc: Feature doc for shard translator) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10537 (doc: Feature doc for shard translator) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/10537 committed in master by Humble Devassy Chirammal (humble.devassy) ------ commit 41c3c1c1e4ccc425ac2edb31d7fa970ff464ebdd Author: Krutika Dhananjay <kdhananj> Date: Tue May 5 07:57:10 2015 +0530 doc: Feature doc for shard translator Source: https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20 Change-Id: I127685bacb6cf924bb41a3b782ade1460afb91d6 BUG: 1200082 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/10537 Reviewed-by: Humble Devassy Chirammal <humble.devassy> Tested-by: Humble Devassy Chirammal <humble.devassy>
REVIEW: http://review.gluster.org/10804 (features/shard: Fix incorrect parameter to get_lowest_block()) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10804 (features/shard: Fix incorrect parameter to get_lowest_block()) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10804 (features/shard: Fix incorrect parameter to get_lowest_block()) posted (#5) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10804 (features/shard: Fix incorrect parameter to get_lowest_block()) posted (#6) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/10804 (features/shard: Fix incorrect parameter to get_lowest_block()) posted (#7) for review on master by Krutika Dhananjay (kdhananj)
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