Bug 878004
Summary: | glusterd segfaults in remove brick | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> | |
Component: | glusterd | Assignee: | krishnan parthasarathi <kparthas> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | medium | |||
Version: | mainline | CC: | amarts, gluster-bugs, nsathyan | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 878873 (view as bug list) | Environment: | ||
Last Closed: | 2013-07-24 17:30:24 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 878873 |
Description
Pranith Kumar K
2012-11-19 12:34:53 UTC
REVIEW: http://review.gluster.org/4885 (tests: Modified test to use remove-brick instead of 'start' variant) posted (#2) for review on master by Krishnan Parthasarathi (kparthas) COMMIT: http://review.gluster.org/4885 committed in master by Vijay Bellur (vbellur) ------ commit f75be775a9b191eb74f6cb4c161d9af36f2fdc97 Author: Krishnan Parthasarathi <kparthas> Date: Thu Apr 25 00:28:07 2013 +0530 tests: Modified test to use remove-brick instead of 'start' variant remove-brick start doesn't remove the brick from the volume immediately. It would wait until migration of data to other bricks are complete. Even when there is no data to be migrated, one can expect a finite delay from the time of remove-brick start command's exit and removal of brick(s). This may cause subsequent checks on brick count to fail in a non-deterministic manner. Also, renamed the test file name to reflect bug-id corresponding to community release. Change-Id: Ic43f011e251640decb68e46f4a10e0824ade0ac9 BUG: 878004 Signed-off-by: Krishnan Parthasarathi <kparthas> Reviewed-on: http://review.gluster.org/4885 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com> REVIEW: http://review.gluster.org/5052 (tests: Modified test to use remove-brick instead of 'start' variant) posted (#1) for review on release-3.4 by Kaushal M (kaushal) COMMIT: http://review.gluster.org/5052 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit 8abe8f794913daa81d9f1dc0ddab26c9c414abf8 Author: Kaushal M <kaushal> Date: Tue May 21 13:01:08 2013 +0530 tests: Modified test to use remove-brick instead of 'start' variant Backport of change f75be77 from master remove-brick start doesn't remove the brick from the volume immediately. It would wait until migration of data to other bricks are complete. Even when there is no data to be migrated, one can expect a finite delay from the time of remove-brick start command's exit and removal of brick(s). This may cause subsequent checks on brick count to fail in a non-deterministic manner. Also, renamed the test file name to reflect bug-id corresponding to community release. BUG: 878004 Change-Id: Ic6e1360ae5a5280d0d7efe8c3e9a0aa57dddb508 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/5052 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> |