Bug 1727755 - Seeing failure due to "getxattr err for dir [No data available]" in rebalance
Summary: Seeing failure due to "getxattr err for dir [No data available]" in rebalance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: RHGS 3.5.z Batch Update 1
Assignee: Susant Kumar Palai
QA Contact: Sayalee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-08 06:09 UTC by Sayalee
Modified: 2020-01-30 06:43 UTC (History)
6 users (show)

Fixed In Version: glusterfs-6.0-23
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-30 06:42:47 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0288 0 None None None 2020-01-30 06:43:02 UTC

Description Sayalee 2019-07-08 06:09:34 UTC
Description of problem:
While running rebalance on a heterogeneous brick volume, saw failure in rebalance due to "[2019-07-05 09:36:55.653538] E [MSGID: 109039] [dht-common.c:4245:dht_find_local_subvol_cbk] 0-vol6-dht: getxattr err for dir [No data available]" error.

Version-Release number of selected component (if applicable):
6.0.7

How reproducible:
1/1

Steps to Reproduce:
1. Create a 2 brick volume, where brick1 is of 20G and brick2 of 5G
2. Fuse mount the volume on a client node.
3. Check the hash layout on the bricks.
4. Start running I/O from the mount point.
5. While the I/O is still in progress, disable the cluster.weighted-rebalance volume option.
6. Let the I/O continue to run and add-brick of 10G to the volume.
7. Trigger rebalance on the volume.
8. Check hash layout on the back-end bricks.

Actual results:
Seeing failure in rebalance 

Expected results:
Rebalance should complete successfully.

Additional info:
sos-reports will be shared.

Comment 4 Susant Kumar Palai 2019-07-16 05:15:24 UTC
upstream patch: https://review.gluster.org/#/c/glusterfs/+/23053/

Comment 15 errata-xmlrpc 2020-01-30 06:42:47 UTC
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/RHBA-2020:0288


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