+++ This bug was initially created as a clone of Bug #1561406 +++
Description of problem:
When rebalance is executed after adding a brick (or some other operation that changes the layout) on a dispersed volume with lookup-optimize enabled, some files are not migrated to the right brick.
Version-Release number of selected component (if applicable): mainline
Steps to Reproduce:
1. Create a disperse volume
2. Enable lookup-optimize
3. Create some files
4. Add new bricks
5. Run rebalance
Some files are not migrated
All files should be migrated
There's a bug in EC that causes the request for trusted.glusterfs.list-node-uuids xattr to be only processed in one subvolume. This causes that the resulting list only contains one of the UUIDs and all the other are set to the null uuid, as if they were down.
Verified this BZ on glusterfs version 3.12.2-9.el7rhgs.x86_64.
When rebalance is executed after adding a brick on a dispersed volume with lookup-optimize enabled, files are getting migrated without any issues to the bricks.
Moving this BZ to Verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.