Bug 807653 - [bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick start after a replace-brick abort fails migrating data
[bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick start after a repla...
Status: CLOSED WORKSFORME
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
pre-release
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: krishnan parthasarathi
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-28 08:13 EDT by Rahul C S
Modified: 2015-12-01 11:45 EST (History)
3 users (show)

See Also:
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:


Attachments (Terms of Use)

  None (edit)
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.

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