[pve-devel] [PATCH manager 2/4] vzdump: storage_info: adapt to new maxfiles backend behavior

Fabian Ebner f.ebner at proxmox.com
Tue Dec 1 09:24:19 CET 2020


It's automatically converted to prune-backups when using storage_config() now.

Signed-off-by: Fabian Ebner <f.ebner at proxmox.com>
---
 PVE/VZDump.pm | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
index c37fa513..94aa76ab 100644
--- a/PVE/VZDump.pm
+++ b/PVE/VZDump.pm
@@ -86,15 +86,11 @@ sub storage_info {
 
     my $info = {
 	scfg => $scfg,
-	maxfiles => $scfg->{maxfiles},
     };
 
     $info->{'prune-backups'} = PVE::JSONSchema::parse_property_string('prune-backups', $scfg->{'prune-backups'})
 	if defined($scfg->{'prune-backups'});
 
-    die "cannot have 'maxfiles' and 'prune-backups' configured at the same time\n"
-	if defined($info->{'prune-backups'}) && defined($info->{maxfiles});
-
     if ($type eq 'pbs') {
 	$info->{pbs} = 1;
     } else {
-- 
2.20.1






More information about the pve-devel mailing list