Bug 807653

Summary: [bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick start after a replace-brick abort fails migrating data
Product: [Community] GlusterFS Reporter: Rahul C S <rahulcs>
Component: glusterdAssignee: krishnan parthasarathi <kparthas>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: gluster-bugs, nsathyan, vkoppad
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-06 07:52:16 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Rahul C S 2012-03-28 08:13:42 EDT
Description of problem:
replace-brick start on the same src/dest brick pair, after a replace-brick abort has been issued does not initiate data migration.

root@Dagobah:~# gluster volume replace-brick vol dagobah:/data/export3 dagobah:/data/export7 status
Number of files migrated = 0       Current file=  
root@Dagobah:~# gluster volume replace-brick vol dagobah:/data/export3 dagobah:/data/export7 status
Number of files migrated = 0       Current file=
Comment 1 Vijaykumar Koppad 2012-04-06 07:52:16 EDT
It works properly in the latest build.