public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage] plugin: file size info: use fallback for actual size
Date: Mon, 28 Nov 2022 16:55:09 +0100	[thread overview]
Message-ID: <20221128155509.142996-1-f.ebner@proxmox.com> (raw)

The actual-size property is an optional property in the QAPI
definition for ImageInfo. If it's not set, simply use the information
from stat() as a fallback. This is essentially the same
raw_get_allocated_file_size() in QEMU does anyways.

Reported in the community forum:
https://forum.proxmox.com/threads/118443/post-513421

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---

Thanks to Mira for setting up a GlusterFS instance and discussing the
issue with me!

I'm not sure why QEMU fails here, didn't see much that could go wrong
beside the fstat() call failing. But our stat() call in the beginning
of file_size_info already succeeded at that point :/ The mysteries of
QEMU+GlusterFS.

Also, it's a bit strange to call qemu-img info regardless of whether
the image is a VM image or not. E.g., this results in the format
property for backups to always be raw, rather than the backup format.
Should we change that (for 8.0)?

 PVE/Storage/Plugin.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/PVE/Storage/Plugin.pm b/PVE/Storage/Plugin.pm
index 8a41df1..7773ac3 100644
--- a/PVE/Storage/Plugin.pm
+++ b/PVE/Storage/Plugin.pm
@@ -899,6 +899,7 @@ sub file_size_info {
     }
 
     my ($size, $format, $used, $parent) = $info->@{qw(virtual-size format actual-size backing-filename)};
+    $used ||= $st->blocks * 512;
 
     ($size) = ($size =~ /^(\d+)$/) or die "size '$size' not an integer\n"; # untaint
     # coerce back from string
-- 
2.30.2





             reply	other threads:[~2022-11-28 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 15:55 Fiona Ebner [this message]
2023-01-11 15:46 ` Thomas Lamprecht
2023-01-12  8:33   ` Fiona Ebner
2023-01-13 11:50     ` Wolfgang Bumiller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221128155509.142996-1-f.ebner@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal