[Bugs] [Bug 1627060] New: ./tests/features/trash.t test case failing on s390x

[bugzilla at redhat.com]

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

            Bug ID: 1627060
           Summary: ./tests/features/trash.t test case failing on s390x
           Product: GlusterFS
           Version: 4.1
         Component: trash-xlator
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: abhaysingh1722 at yahoo.in
                CC: bugs at gluster.org



Created attachment 1482096
  --> https://bugzilla.redhat.com/attachment.cgi?id=1482096&action=edit
patchy-rebalance.log for s390x

Description of problem:
I am working on Glusterfs v4.1.1 for all distributions on s390x architecture.
After successful build and running the test cases, I encountered a test case
failure. The subtests 39,63 of ./tests/features/trash.t are failing with the
following errors:-
=========================
TEST 37 (line 190): 0 rebalance_completed
ok 37, LINENUM:190
RESULT 37: 0
ls: cannot access '/d/backends/patchy3/rebal*': No such file or directory
basename: missing operand
Try 'basename --help' for more information.
=========================
TEST 38 (line 196): Y wildcard_exists /d/backends/patchy3/1
/d/backends/patchy3/a
ok 38, LINENUM:196
RESULT 38: 0
=========================
TEST 39 (line 197): Y wildcard_exists
/d/backends/patchy1/.trashcan/internal_op/*
not ok 39 Got "N" instead of "Y", LINENUM:197
RESULT 39: 1
=========================

=========================
TEST 63 (line 247): Y wildcard_exists
/d/backends/patchy1/abc/internal_op/rebal*
not ok 63 Got "N" instead of "Y", LINENUM:247
RESULT 63: 1
rm: cannot remove '/mnt/glusterfs/0/abc/internal_op': Operation not permitted
=========================

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

How reproducible:
Build Glusterfs v4.1.1 and run the test case with ./run-tests.sh prove -vf
./tests/features/trash.t


Steps to Reproduce:
1./run-tests.sh prove -vf ./tests/features/trash.t


Actual results:
Test fails with the above mentioned errors.


Expected results:
Test passes


Additional info:
As per my understanding the test case attempts to migrate rebal2 from
/d/backends/patchy3/ to /d/backends/patchy1/.trashcan/internal_op/. Test case
fails because rebal2 is not getting migrated on s390x.

After debugging and understanding the flow of the execution of the test, it was
found that the rebalance operation when the test case is run fails. I found out
that this is because the hashed subvol for patchy is getting wrongly calculated
for s390x systems while migrating the file.

On big endian systems, the log says:
[dht-rebalance.c:2823:gf_defrag_migrate_single_file] 0-patchy-dht: Attempting
to migrate data (null) with gfid 00000000-0000-0000-0000-000000000001 from
patchy-client-0 -> patchy-client-0
On little endian systems, the log says:
[dht-rebalance.c:2823:gf_defrag_migrate_single_file] 0-patchy-dht: Attempting
to migrate data (null) with gfid 00000000-0000-0000-0000-000000000001 from
patchy-client-0 -> patchy-client-1


Tried following resolutions:-
1.Ran the test case on an xfs backend
2.Increasing thread_stack_size to check if its a stack overflow issue.

But the test still fails.

I am providing you with the patchy-rebalance.log for both the little endian and
big-endian systems.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.