Page MenuHomePhabricator

Disk space low in cloudvirt10[19-20]
Closed, ResolvedPublic

Description

The libvirt snapshots I created in T329970 are copy-on-write snapshots that didn't use any disk space initially, but are using a growing amount of space that means we now have less than 5% free disk space on both cloudvirt1019 and cloudvirt1020.

We could merge the different qcow2 snapshot files into a single file (documentation here):

virsh blockcommit vm1 vda --verbose --pivot --active

I have two concerns:

  1. it's not clear if that operation requires a bigger amount of free disk space than what we have now
  2. while it can be performed live, it could have an impact on database performance

I'm thinking of just freeing up some space on disk instead, so that the snapshot can continue to grow for a few more weeks, until we decommission both servers.

There are about 1.5TB that are used by the disk images of clouddb1003 and clouddb1004. Those VMs were deprecated and stopped in T323159, so I believe that after 1 month we can now delete those disk images and free up 1.5TB on both hypervisors (cloudvirt1019 and cloudvirt1020).

Event Timeline

@Andrew are you ok with me deleting those disks (the old OSMdb instances)? If we wanted to keep a backup, I could copy the content to a Cinder volume, but I'm not sure it's worth it.

fnegri closed this task as Resolved.EditedMar 28 2023, 8:23 PM

Discussed in IRC, @Andrew deleted both clouddb1003 and clouddb1004, and free space is back at about 30% on both cloudvirt1019 and cloudvirt1020.

As we plan to decom both cloudvirts soon (T301949), I don't think there's any other action needed.