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

bugzilla at redhat.com bugzilla at redhat.com
Mon Nov 12 07:24:47 UTC 2018


Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
              Flags|                            |needinfo?(abhaysingh1722 at ya
                   |                            |hoo.in)

--- Comment #14 from Nithya Balachandran <nbalacha at redhat.com> ---
(In reply to abhays from comment #13)
> Hi,
> Thanks for the code you provided.
> The following are the hash values I am getting:-
> ./hashcompute /d/backends/patchy1/rebal2
> Name = /d/backends/patchy1/rebal2, hash = 3197287436, (hex = 0xbe92bc0c)
> ./hashcompute /d/backends/patchy1
> Name = /d/backends/patchy1, hash = 269829764, (hex = 0x10154684)
> ./hashcompute /d/backends/patchy3
> Name = /d/backends/patchy3, hash = 1798194767, (hex = 0x6b2e464f)
> Note:-Since rebal2 isn't getting migrated from patchy1 to patchy3, I have
> provided the hash values accordingly.

The way dht works is as follows:
Each directory is created on each brick
A layout spanning 0x00000000 to 0xffffffff is divided between the bricks.
The directory on each brick is assigned a layout - a hash range which is stored
in the xattr trusted.dht
For example :

(I have used [] to demarcate the start and stop of the range assigned as per
the xattr.)

To decide where to place a file on the volume, dht calculates the hash of the
filename and finds the brick on which the layout of the parent directory
contains the range into which which the hash falls.

I only need the hash value of rebal2 and the xattrs on the brick roots after
the rebalance is run.

Can you run the hashcompute on an x86  system and let me know the value for
rebal2 as well?

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=IlI6bMYtNW&a=cc_unsubscribe

More information about the Bugs mailing list