Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1561733 - Rebalance failures on a dispersed volume with lookup-optimize enabled
Rebalance failures on a dispersed volume with lookup-optimize enabled
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: disperse (Show other bugs)
3.4
Unspecified Unspecified
urgent Severity urgent
: ---
: RHGS 3.4.0
Assigned To: Xavi Hernandez
Prasad Desala
:
Depends On: 1561406
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-03-28 14:47 EDT by Xavi Hernandez
Modified: 2018-09-04 04:22 EDT (History)
9 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-7
Doc Type: Bug Fix
Doc Text:
Previously, when lookup-optimize was enabled, some files were not migrated on a disperse volume due to incomplete data returned by a special rebalance request. This fix ensures that all required data is transferred and all files are migrated.
Story Points: ---
Clone Of: 1561406
Environment:
Last Closed: 2018-09-04 02:45:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 02:46 EDT

  None (edit)
Description Xavi Hernandez 2018-03-28 14:47:58 EDT
+++ 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


How reproducible:

Always

Steps to Reproduce:
1. Create a disperse volume
2. Enable lookup-optimize
3. Create some files
4. Add new bricks
5. Run rebalance

Actual results:

Some files are not migrated

Expected results:

All files should be migrated

Additional info:

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.
Comment 6 Prasad Desala 2018-05-11 05:25:17 EDT
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.
Comment 10 errata-xmlrpc 2018-09-04 02:45:40 EDT
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.

https://access.redhat.com/errata/RHSA-2018:2607

Note You need to log in before you can comment on or make changes to this bug.