+++ This bug was initially created as a clone of Bug #1471031 +++
Description of problem:
Sharding uses xattrops to set the size info on the file. DHT does not currently implement migration phase1/phase2 checks for these and can possibly lead to issues when sharding is enabled.
REVIEW: https://review.gluster.org/19174 (cluster/dht: Add migration checks to dht_(f)xattrop) posted (#1) for review on release-3.10 by N Balachandran
COMMIT: https://review.gluster.org/19174 committed in release-3.10 by "N Balachandran" <firstname.lastname@example.org> with a commit message- cluster/dht: Add migration checks to dht_(f)xattrop
The dht_(f)xattrop implementation did not implement
migration phase1/phase2 checks which could cause issues
with rebalance on sharded volumes.
This does not solve the issue where fops may reach the target
out of order.
> Change-Id: I2416fc35115e60659e35b4b717fd51f20746586c
> BUG: 1471031
> Signed-off-by: N Balachandran <email@example.com>
Signed-off-by: N Balachandran <firstname.lastname@example.org>
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.10.10, please open a new bug report.
glusterfs-3.10.10 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.