Bug 1622681
Summary: | Unable to delete pvc from a block hosting volume which is very low in available space | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Neha Berry <nberry> |
Component: | gluster-block | Assignee: | Prasanna Kumar Kalever <prasanna.kalever> |
Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.10 | CC: | akrishna, bgoyal, bkunal, hchiramm, jmulligan, jpankaja, kramdoss, madam, nberry, pkarampu, pprakash, prasanna.kalever, psony, rhs-bugs, rtalur, sankarshan, vbellur, xiubli |
Target Milestone: | --- | ||
Target Release: | CNS 3.10 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gluster-block-0.2.1-26.el7rhgs | Doc Type: | Bug Fix |
Doc Text: |
Previously, if the block volume was attempted for delete when block hosting volume was 100% consumed, the delete operation failed. Because the writes to metadata file residing in the same block hosting volume failed with ENOSPC and hence the overall delete operation failed. Now, with this fix at every new block volume create request, the gluster-block checks for minimum free space equal to 'requested block volume size' + 10M which is reserved for block metadata on the block hosting volume, this way block volume delete will succeed even when block hosting volume is almost full.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-12 09:27:16 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 |
Description
Neha Berry
2018-08-27 18:02:47 UTC
Have updated the doc text, kindly review. 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:2691 |