Bug 1596018
| Summary: | Block device creation fails with sufficient space available on the devices | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rachael <rgeorge> |
| Component: | heketi | Assignee: | Michael Adam <madam> |
| Status: | CLOSED ERRATA | QA Contact: | vinutha <vinug> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | cns-3.9 | CC: | akrishna, hchiramm, jmulligan, kramdoss, madam, nberry, rgeorge, rhs-bugs, rtalur, sankarshan, sarumuga, sselvan, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | CNS 3.10 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the logic in Heketi incorrectly assumed block volumes always fit within block hosting volumes if the size of the block volume was smaller than the total size of the hosting volume minus the sizes of the existing block volumes. This logic failed to account for the fact that the file system and the block volumes contained within it require space to manage metadata. Trying to place such a volume failed with an out of space error instead of allocating a new block hosting volume. With this fix, Heketi reserves a small percentage of the total size of the block hosting volume for metadata.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-12 09:23:45 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: | 1568862 | ||
|
Comment 2
Rachael
2018-06-28 06:47:28 UTC
Do we have an automated test for this? Sounds like a simple use case? As of today we don't have this test case automated. Rachael, was auto create block hosting volume option set to true? *** Bug 1607551 has been marked as a duplicate of this bug. *** as per comment #17 Updated doc text in the Doc Text field. Please review for technical accuracy. Updated doc text in the Doc Text field. Please review for technical accuracy. Hi John, I have updated the doc text. Thank you! 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-2018:2686 |