Backlog #2737

Consider Storage allocation USED vs ALLOCATED datastore capacity

Added by Boris Parak over 7 years ago. Updated over 3 years ago.

Status:PendingStart date:02/19/2014
Priority:SponsoredDue date:
Assignee:-% Done:

0%

Category:Drivers - Storage
Target version:-

Description

Running the disk-attach action with disks larger than the available datastore capacity fails with 'Error copying' and there is no clean-up. After a few attempts, hosts start filling up with useless data.

Related issues

Related to Backlog #2402: Keep track of allocated storage in DS Pending 10/23/2013

History

#1 Updated by Carlos Martín over 7 years ago

  • Category changed from Core & System to Drivers - Storage
  • Status changed from Pending to New
  • Target version set to Release 4.6

For now, the storage usage is not enforced by the core, only by the scheduler. This will be addressed in #2402.

But I'm planning it for 4.6 to see if the drivers could try to clean up after a failed copy.

#2 Updated by Carlos Martín over 7 years ago

  • Related to Backlog #2402: Keep track of allocated storage in DS added

#3 Updated by Boris Parak over 7 years ago

Carlos Martín wrote:

For now, the storage usage is not enforced by the core, only by the scheduler. This will be addressed in #2402.

That would be great.

But I'm planning it for 4.6 to see if the drivers could try to clean up after a failed copy.

Perhaps, failing instantly wouldn't be a bad idea either. Just a simple call to

df PATH_TO_TARGET

should give enough information for a quick ad-hoc decision.

#4 Updated by Jaime Melis over 7 years ago

  • Target version changed from Release 4.6 to Release 4.8

#5 Updated by Ruben S. Montero about 7 years ago

  • Assignee set to Carlos Martín

#6 Updated by Ruben S. Montero almost 7 years ago

  • Tracker changed from Bug to Backlog
  • Subject changed from disk-attach action on running VMs ignores datastore capacity to Consider Storage allocation USED vs ALLOCATED datastore capacity

This will be address by computing image sizes in the core and cross-check with it before an image movement. Operations like disk-attach and deployment will no ignore the allocated capacity

#7 Updated by Ruben S. Montero almost 7 years ago

  • Status changed from New to Pending
  • Assignee deleted (Carlos Martín)
  • Priority changed from Normal to High
  • Target version deleted (Release 4.8)

#8 Updated by Ruben S. Montero over 3 years ago

  • Priority changed from High to Sponsored

Also available in: Atom PDF