Bug 1161104 - replace-brick start causes gluster to hang
Summary: replace-brick start causes gluster to hang
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.5.2
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-06 11:39 UTC by Hemant
Modified: 2016-06-17 15:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 15:57:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Hemant 2014-11-06 11:39:53 UTC
Description of problem: After the execution of remove-brick start, gluster service suffers from hang problem. No output is displayed as the result of operation. Furthur, none of the gluster command works fine untill gluster service is restarted.
After restarting the gluster service system behaves properly.

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


How reproducible: Each time replce-brick start is executed.


Steps to Reproduce:
1. glluster volume replace-brick volume_name old_brick new_brick start
2.
3.

Actual results: No output is displayed.


Expected results: After execution it should show replace brick start operation successful


Additional info:

Comment 1 Lalatendu Mohanty 2014-11-11 12:53:41 UTC
Looks like a duplicate of BZ 1162479

Comment 2 Niels de Vos 2016-06-17 15:57:04 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


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