+++ This bug was initially created as a clone of Bug #1350365 +++
Description of problem:
In comments of the patch http://review.gluster.org/14623, Krutika found that this bug needs to be fixed. Raising this bug to track this issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
From a comment in http://review.gluster.org/14623:
> > > With this patch, we run the risk of creating extra shards (beyond the
> > > size of the file) leading to unlink/rename missing to delete the shard.
> > Yes, Reads shoudn't create shards. If we take care of that, it will be
> > fixed.
> Is there a bug for this? I guess should only include this patch and the fix
> for the mentioned problem in stable branches when both fixes are available?
I will raise a bug for that. Without this patch Hyper-convergence feature won't
work at all on gluster because of o-direct files writes. So merge this patch as
without it, 3.7 works, master works but 3.8 will be broken.
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
This bug did not make it in the glusterfs-3.8.6 release and has been moved to the 3.8.7 planning.
This bug did not make it in the glusterfs-3.8.7 release and has been moved to the 3.8.8 planning.
This bug did not make it in the glusterfs-3.8.8 release and has been moved to the 3.8.9 planning.
This bug did not make it in the glusterfs-3.8.9 release and has been moved to the 3.8.10 planning.
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.