Bug 1477431
Summary: | After Volume Expansion is completed successfully getting write error inside the volume | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Tejas Chaphekar <tchaphek> |
Component: | heketi | Assignee: | Mohamed Ashiq <mliyazud> |
Status: | CLOSED ERRATA | QA Contact: | Tejas Chaphekar <tchaphek> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.6 | CC: | asriram, hchiramm, madam, mliyazud, pprakash, rhs-bugs, rtalur, srmukher, storage-qa-internal, vinug |
Target Milestone: | --- | ||
Target Release: | CNS 3.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | heketi-5.0.0-7 rhgs-volmanager-docker-5.0.0-9 | Doc Type: | Bug Fix |
Doc Text: |
Prior to this update, after expansion of a volume using heketi-cli, rebalance of volume was not performed which led to write errors on files that resided on old bricks. With this fix, a rebalance operation is initiated on the volume after every expansion.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-11 07:09:46 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: | 1440900, 1445448 |
Description
Tejas Chaphekar
2017-08-02 04:55:06 UTC
As per Humble's suggestion i ran a manual re-balance of the volume from the gluster pod and after that i am able to utilize the expanded storage. But the volume re-balance should be happening automatically as a part of volume expansion operation which is not the case as of now With new builds i am able to perform a volume expansion and write data onto new bricks without doing a manual re-balance Performed following scenarios 1. Performed Volume expansion, created a new file and directory and perform I/O inside existing directories 2. Created new directories under the mount point and performed I/O. 3. Performed a volume expansion when the volume is full and performed I/O 4. Performed a volume expansion before volume is full and performed I/O Following builds were used for the verification heketi-client-5.0.0-7.el7rhgs.x86_64 cns-deploy-5.0.0-14.el7rhgs.x86_64 Gluster - rhgs-server-rhel7:3.3.0-11 Heketi - rhgs-volmanager-rhel7:3.3.0-9 With new builds i am able to perform a volume expansion and write data onto new bricks without doing a manual re-balance Performed following scenarios 1. Performed Volume expansion, created a new file and directory and perform I/O inside existing directories 2. Created new directories under the mount point and performed I/O. 3. Performed a volume expansion when the volume is full and performed I/O 4. Performed a volume expansion before volume is full and performed I/O Following builds were used for the verification heketi-client-5.0.0-7.el7rhgs.x86_64 cns-deploy-5.0.0-14.el7rhgs.x86_64 Gluster - rhgs-server-rhel7:3.3.0-11 Heketi - rhgs-volmanager-rhel7:3.3.0-9 Thanks a lot Tejus for the update!! doc text looks good to me Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2879 |