error rbd image size lead to too big system volume
Bug #1321271 reported by
ling-yun
This bug report is a duplicate of:
Bug #1219658: Wrong image size using rbd backend for libvirt.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Undecided
|
ling-yun | ||
Bug Description
If you create a vm with 20G disk using rbd as imagebackend, it would create an rbd image with 20480G (real size = configured size * 1024).
Beside the problem of wrong size allocation, this bug also bring two side effect:
1. The vm consume more disk space than configured size, which would lead to an worst case scenario that serveral vm instance would take up all the volume backend free space if they are writing data to rbd image.
2. It would make delete vm operation seems like being stuck because deleting all the objects of a rbd image with a too big size cost a lot of time.
| Changed in nova: | |
| assignee: | nobody → ling-yun (zengyunling) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on nova (master) | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/