Bug 765307 (GLUSTER-3575) - Replace-brick is not happening properly
Summary: Replace-brick is not happening properly
Keywords:
Status: CLOSED DUPLICATE of bug 765289
Alias: GLUSTER-3575
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 13:28 UTC by Vijaykumar
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Vijaykumar 2011-09-16 13:28:16 UTC 
When you do replace-brick , it is migrating only top level entries , not the data.

Volume Name: dht
Type: Distribute
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: openstack2:/home/gluster/bricks/dht/d3
Brick2: openstack2:/home/gluster/bricks/dht/d2
Comment 1 krishnan parthasarathi 2011-09-17 08:20:49 UTC 
Vijaykumar,

What do you mean when you say top level entries? Can you clarify if the directory
tree structure is the same in both source and destination brick after replace-brick operation completes?
Comment 2 Vijaykumar 2011-09-19 02:13:54 UTC 
I mean by top level entries is, only first level of directories are copied not the sub directories.
Comment 3 Vijaykumar 2011-09-19 03:04:32 UTC 
Its happening in 3.3.0qa9 also.
Comment 4 Vijaykumar 2011-09-19 03:52:58 UTC 
Since i can't proceed with some of the other test cases, i am moving it to critical.
Comment 5 krishnan parthasarathi 2011-10-13 08:54:42 UTC 

*** This bug has been marked as a duplicate of bug 3557 ***
Note You need to log in before you can comment on or make changes to this bug.