Bug 1049864
Summary: | Creating a 99G volume on 100G cinder-volume succeeded, but deleting it failed (no space left) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] RDO | Reporter: | Meital Bourvine <mbourvin> | ||||
Component: | openstack-cinder | Assignee: | Eric Harney <eharney> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Dafna Ron <dron> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | unspecified | CC: | eharney, nlevinki, yeylon, zaitcev | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-03-18 18:21:39 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: | |||||||
Attachments: |
|
Description
Meital Bourvine
2014-01-08 11:47:11 UTC
Created attachment 847084 [details]
cinder volume log
This could be due to disk space constraints on the system. Can you post the output of "df", "vgs", "lvs", and "losetup -a"? The delete process for Cinder LVM-backed volumes writes over the full amount of data during deletion, so it will write 99G of data in this case. If the VG is backed by a loopback file it is possible that the file system filled up, causing the Swift error seen above. I re-provisioned my machine, so I can't provide this info. What you wrote is probably the case, but I don't understand something - shouldn't it write the zeros on the existing volume? We already have 99G for this volume. Yes, but it is possible to have a 99G volume that is backed by a file on a file system smaller than 99G. Packstack will do this by default I believe (with a 20G configuration). An empty file is created which is mounted as a loopback device, and then the volume group is created on top of that. But the VG can be larger than the underlying file system, which is why this can occur when lots of data is written to it. Seems to be explained by comment #4. |