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

bugzilla at redhat.com bugzilla at redhat.com
Mon Nov 12 05:30:54 UTC 2018


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



--- Comment #8 from abhays <abhaysingh1722 at yahoo.in> ---
(In reply to Nithya Balachandran from comment #6)
> (In reply to abhays from comment #4)
> > (In reply to Nithya Balachandran from comment #3)
> > > (In reply to abhays from comment #2)
> > > > Hi,
> > > > 
> > > > Any updates on the issue??
> > > > Please let us know if any additional info is needed from our side.
> > > > Can you please take it on priority as the test failure is blocking our work
> > > > on the package.
> > > 
> > > Please provide the following:
> > > 
> > > 1. the value of the calculated hash on both big and little endian systems.
> > > 2. The 'getfattr -e hex -m . -d ' output for the directories on each brick.
> > 
> > Nithya,
> > 
> > 1. I am not sure what exactly the hash values are getting calculated as on
> > big endian. It'll be really helpful if you could help me with that.
> > However, while debugging the test case ./tests/basic/namespace.t, I did
> > encounter hashes which were getting differently calculated for big endian
> > systems.These values are as follows(for big endian):-
> > NAMESPACE_HASH=3253352021
> > NAMESPACE2_HASH=458775276
> > NAMESPACE3_HASH=1268089390
> 
> What are NAMESPACE(2,3)? I would need the name of the file and the hash
> calculated for the same on the big endian system.
> 
> In this case, the file is rebal2. Please provide the hash calculated on the
> big endian system.
> 
> On my x86 system, I get the following which would mean the rebalance would
> have migrated it to patchy3.
> 
> ./hashcompute rebal2
> Name = rebal2, hash = 244726431, (hex = 0x0e963a9f)

Thanks for the reply Nithya.

I am not sure how is the hash value calculated for the folder.
The NAMESPACE_HASH, NAMESPACE2_HASH, NAMESPACE3_HASH values have been verified
from the logs generated for big endian systems from the path
"/var/log/glusterfs/bricks/d-backends-$BRICK.log" after running the
./tests/basic/namespace.t test case.

PFA the patchy3 logs.

Also, I couldn't find the script you have mentioned to compute the hash
anywhere i.e. ./hashcompute rebal2.
Could you please provide any other way in which I can do the same.
Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=q7bjh6eCkq&a=cc_unsubscribe


More information about the Bugs mailing list