Bug 1070573 - layout is missing when add-brick is done,new created files only locate on old bricks
Summary: layout is missing when add-brick is done,new created files only locate on old...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: SATHEESARAN
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-27 06:27 UTC by Jiale Gao
Modified: 2014-03-06 12:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-06 12:02:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jiale Gao 2014-02-27 06:27:28 UTC
Description of problem:
layout is missing when add-brick is done,new created files only locate on old bricks

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


How reproducible:


Steps to Reproduce:
1.create a new volume and touch a few files at client.
2.do add-brick to add some bricks
3.stat the creaeted files and touch some new files.

Actual results:
no dht-link found on the new brick, and the new created files only located on old bricks.
use getfattr to check the bricks path,layout is still missing without fixed.


Expected results:
we could use the new created bricks immediately when add-brick is done.

Additional info:

Comment 1 SATHEESARAN 2014-03-06 12:02:55 UTC
This is the expected behaviour with Distribute volumes

1. When you add a new brick to the distribute volume, you need to do "fix-layout",
to make use of newly added brick.

(i.e) gluster volume rebalance <vol-name> fix-layout start

The above command fixes the layout and new brick will be used for consumption

2. If you trigger rebalance, that triggers the fix-layout and then migrates the old files also

(i.e) gluster volume rebalance <vol-name> start

Considering the above, moving this bug as NOT-A-BUG


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