[Bugs] [Bug 1548078] New: [Rebalance] "Migrate file failed: <filepath>: failed to get xattr [No data available]" warnings in rebalance logs

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1548078

            Bug ID: 1548078
           Summary: [Rebalance] "Migrate file failed: <filepath>: failed
                    to get xattr [No data available]" warnings in
                    rebalance logs
           Product: GlusterFS
           Version: 3.12
         Component: distribute
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: nbalacha at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    storage-qa-internal at redhat.com, tdesala at redhat.com
        Depends On: 1546954
            Blocks: 1546945



+++ This bug was initially created as a clone of Bug #1546954 +++

+++ This bug was initially created as a clone of Bug #1546945 +++

Description of problem:
=======================
After rebalance is triggered on the volume, on few files I am seeing below
warnings in rebalance logs,

[2018-02-20 05:35:39.439245] W [MSGID: 109023]
[dht-rebalance.c:2036:dht_migrate_file] 0-distrepx3-dht: Migrate file
failed:/1/linux-4.6.4/Documentation/devicetree/bindings/mfd/arizona.txt: failed
to get xattr from distrepx3-replicate-2 [No data available]
[2018-02-20 05:35:39.699443] W [MSGID: 109023]
[dht-rebalance.c:2036:dht_migrate_file] 0-distrepx3-dht: Migrate file
failed:/1/linux-4.6.4/Documentation/devicetree/bindings/mfd/da9055.txt: failed
to get xattr from distrepx3-replicate-2 [No data available]
[2018-02-20 05:35:40.056391] W [MSGID: 109023]
[dht-rebalance.c:2036:dht_migrate_file] 0-distrepx3-dht: Migrate file
failed:/1/linux-4.6.4/Documentation/devicetree/bindings/mfd/tps6507x.txt:
failed to get xattr from distrepx3-replicate-2 [No data available]
[2018-02-20 05:35:42.952071] W [MSGID: 109023]
[dht-rebalance.c:2036:dht_migrate_file] 0-distrepx3-dht: Migrate file
failed:/1/linux-4.6.4/Documentation/devicetree/bindings/mmc/mmc-card.txt:
failed to get xattr from distrepx3-replicate-2 [No data available]
[2018-02-20 05:35:43.019614] W [MSGID: 109023]
[dht-rebalance.c:2036:dht_migrate_file] 0-distrepx3-dht: Migrate file
failed:/1/linux-4.6.4/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt:
failed to get xattr from distrepx3-replicate-0 [No data available]

I am seeing may such warnings in the rebalance logs and logs will get flooded
with these warnings if we have large dataset.


How reproducible:
1/1

Steps to Reproduce:
===================
1) Create a x3 volume and start it.
2) FUSE mount it on multiple clients.
3) Run linux kernel untar from two clients .
4) While IO is in-progress, add bricks to the volume and start rebalance
without force.

Actual results:
===============
Seeing, "Migrate file failed: <filepath>: failed to get xattr [No data
available]" warnings in rebalance logs

Expected results:
================
Should not see the above mentioned warnings

--- Additional comment from Worker Ant on 2018-02-20 09:46:23 EST ---

REVIEW: https://review.gluster.org/19603 (cluster/dht: Ignore ENODATA from
getxattr for posix acls) posted (#1) for review on master by N Balachandran

--- Additional comment from Worker Ant on 2018-02-22 05:50:36 EST ---

COMMIT: https://review.gluster.org/19603 committed in master by "Raghavendra G"
<rgowdapp at redhat.com> with a commit message- cluster/dht: Ignore ENODATA from
getxattr for posix acls

dht_migrate_file no longer prints an error if getxattr for
posix acls fails with ENODATA/ENOATTR.

Change-Id: Id9ecf6852cb5294c1c154b28d609889ea3420e1c
BUG: 1546954
Signed-off-by: N Balachandran <nbalacha at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1546945
[Bug 1546945] [Rebalance] "Migrate file failed: <filepath>: failed to get
xattr [No data available]" warnings in rebalance logs
https://bugzilla.redhat.com/show_bug.cgi?id=1546954
[Bug 1546954] [Rebalance] "Migrate file failed: <filepath>: failed to get
xattr [No data available]" warnings in rebalance logs
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.