yahoo-eng-team team mailing list archive

[ling-yun <zengyunling@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
     Assignee: ling-yun (zengyunling)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => ling-yun (zengyunling)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1321271

Title:
  error rbd image size lead to too big system volume

Status in OpenStack Compute (Nova):
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1321271/+subscriptions