From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH storage 1/2] api2/storage/content: change to volume_size_info and add return properties
Date: Fri, 13 Nov 2020 10:38:50 +0100 [thread overview]
Message-ID: <20201113093852.28788-4-d.csapak@proxmox.com> (raw)
In-Reply-To: <20201113093852.28788-1-d.csapak@proxmox.com>
'file_size_info' only works for directory based storages, while
'volume_size_info' should work for all
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
PVE/API2/Storage/Content.pm | 29 ++++++++++++++++++++++++++---
1 file changed, 26 insertions(+), 3 deletions(-)
diff --git a/PVE/API2/Storage/Content.pm b/PVE/API2/Storage/Content.pm
index 8d2ff32..8eeb2eb 100644
--- a/PVE/API2/Storage/Content.pm
+++ b/PVE/API2/Storage/Content.pm
@@ -263,7 +263,30 @@ __PACKAGE__->register_method ({
},
},
},
- returns => { type => 'object' },
+ returns => {
+ type => 'object',
+ properties => {
+ path => {
+ description => "The Path",
+ type => 'string',
+ },
+ size => {
+ description => "Volume size in bytes.",
+ type => 'integer',
+ renderer => 'bytes',
+ },
+ used => {
+ description => "Used space. Please note that most storage plugins " .
+ "do not report anything useful here.",
+ type => 'integer',
+ renderer => 'bytes',
+ },
+ format => {
+ description => "Format identifier ('raw', 'qcow2', 'subvol', 'iso', 'tgz' ...)",
+ type => 'string',
+ },
+ },
+ },
code => sub {
my ($param) = @_;
@@ -277,8 +300,8 @@ __PACKAGE__->register_method ({
PVE::Storage::check_volume_access($rpcenv, $authuser, $cfg, undef, $volid);
my $path = PVE::Storage::path($cfg, $volid);
- my ($size, $format, $used, $parent) = PVE::Storage::file_size_info($path);
- die "file_size_info on '$volid' failed\n" if !($format && $size);
+ my ($size, $format, $used, $parent) = PVE::Storage::volume_size_info($cfg, $volid);
+ die "volume_size_info on '$volid' failed\n" if !($format && $size);
# fixme: return more attributes?
return {
--
2.20.1
next prev parent reply other threads:[~2020-11-13 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 9:38 [pbs-devel] [PATCH proxmox-backup/pve-storage/manager] show/edit backup comments Dominik Csapak
2020-11-13 9:38 ` [pbs-devel] [PATCH proxmox-backup 1/2] client/http_client: add put method Dominik Csapak
2020-11-16 16:01 ` [pbs-devel] applied: " Thomas Lamprecht
2020-11-13 9:38 ` [pbs-devel] [PATCH proxmox-backup 2/2] client: add 'snapshot notes show/update' command Dominik Csapak
2020-11-16 9:37 ` [pbs-devel] [pve-devel] " Thomas Lamprecht
2020-11-16 9:42 ` Dominik Csapak
2020-11-16 10:14 ` Thomas Lamprecht
2020-11-13 9:38 ` Dominik Csapak [this message]
2020-11-13 9:38 ` [pbs-devel] [PATCH storage 2/2] Storage/Plugin: add get/update_volume_comment and implement for dir/pbs Dominik Csapak
2020-11-13 9:38 ` [pbs-devel] [PATCH manager 1/1] ui: add ability to show and edit comments for backups Dominik Csapak
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=20201113093852.28788-4-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-devel@lists.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