Hello all, On 2016-01-24 T 16:25 -0700 Chris Murphy wrote:
On Sun, Jan 24, 2016 at 2:40 PM, Uzair Shamim wrote:
While /var/lib/libvirt/images is on btrfs, its put in a subvolume by default. Doesn't this mean it wont be part of the regular snapshots? - From what I understood things in subvolumes aren't subject to snapshots users take with snapper.
Ahh, I don't have an openSUSE install handy at the moment. Oops. Yes if the images are contained in a subvolume other than the top level of the file system, then top level snapshots done by snapper do not recursively snapshot the contents of nested subvolumes.
indeed.
But what does still happen is VM images cause data chunks to be allocated faster than metadata chunks as the VM image grows. So it's possible to fill up a volume with a high data to metadata chunk ratio that isn't released even if most of the VM's are deleted. You'd have a lot of nearly empty data chunks but can still have totally full metadata chunks and end up with ENOSPC.
That's correct in theory, however as a "proactive remedy", subvolumes such as /var/lib/libvirt should be marked as "NoCOW", to reduce fragmentation and metadata overhead. If this is not the case in Tumbleweed yet, I suggest to open a bugreport (you can check with "lsattr -a /var/lib/libvirt"). So long - MgE -- Matthias G. Eckermann, Director Product Management SUSE Linux Enterprise SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org