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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
Sharding has been working fine in Hyperconverged setup for a long time now. Marking it as WORKSFORME. Reopen if this is still an issue.