Bug 1668327 - Files are not placed at correct hash location in back-end bricks
Summary: Files are not placed at correct hash location in back-end bricks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Nithya Balachandran
QA Contact: Sayalee
URL:
Whiteboard:
: 1679809 (view as bug list)
Depends On:
Blocks: 1290124 1679809
TreeView+ depends on / blocked
 
Reported: 2019-01-22 13:00 UTC by Sayalee
Modified: 2019-03-27 03:44 UTC (History)
12 users (show)

Fixed In Version: glusterfs-3.12.2-46
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-27 03:43:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1679809 1 None None None 2024-09-18 00:50:13 UTC
Red Hat Product Errata RHBA-2019:0658 0 None None None 2019-03-27 03:44:49 UTC

Description Sayalee 2019-01-22 13:00:35 UTC
Description of problem:
Created a dis-rep volume, where one replica set consists of 20GB bricks and second replica set consists of 5GB bricks, after that I FUSE mounted the volume and created three files such that they will hash to second replica set as per the hash layout, but I am seeing the files are created on replica set one.

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

How reproducible:
1/1

Steps to Reproduce:
1) A distributed-replicated volume is created where one replica set has all bricks of 20GB and the other has one brick of 10BG and two bricks of 5GB each.
2) Checked the hash layout on all the bricks.
3) As replica pair of heterogeneous bricks is not supported, did remove-brick to remove the second replica set which had one brick of 10BG and two bricks of 5GB each.
4) Remove brick completed and committed.
5) Added new replica set with all 3 bricks of 5GB each.
6) Triggered rebalance on the volume and it completed successfully.
7) Checked the hash layout on back end bricks.
8) Created three files such that they should hash to the second replica pair, with all 3 bricks of 5GB each.

Actual results:
Files hash at replica set one where all bricks are of 20GB

Expected results:
Files should hash to replica set two with all 3 bricks of 5GB each

Additional info:
sos reports will be shared

Comment 16 Nithya Balachandran 2019-03-26 07:50:10 UTC
*** Bug 1679809 has been marked as a duplicate of this bug. ***

Comment 18 errata-xmlrpc 2019-03-27 03:43:40 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-2019:0658


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