public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Oguz Bektas <o.bektas@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] vzdump: allow backups on btrfs
Date: Mon, 19 Jul 2021 14:57:15 +0200	[thread overview]
Message-ID: <15a01769-c3b9-5b20-b9cb-62ca8c1fb3a1@proxmox.com> (raw)
In-Reply-To: <20210719115859.735216-1-o.bektas@proxmox.com>

On 19.07.21 13:58, Oguz Bektas wrote:
> see forum post [0]
> 
> [0]:
> https://forum.proxmox.com/threads/cant-use-storage-type-btrfs-for-backup-500-help.92918/
> 
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
>  PVE/VZDump.pm | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
> index 46cb9e6d..39b5e46d 100644
> --- a/PVE/VZDump.pm
> +++ b/PVE/VZDump.pm
> @@ -102,7 +102,8 @@ sub storage_info {
>  
>      die "can't use storage type '$type' for backup\n"
>  	if (!($type eq 'dir' || $type eq 'nfs' || $type eq 'glusterfs'
> -	      || $type eq 'cifs' || $type eq 'cephfs' || $type eq 'pbs'));
> +	      || $type eq 'cifs' || $type eq 'cephfs' || $type eq 'pbs'
> +	      || $type eq 'btrfs'));

Rather, that whole check above needs to be removed, we can derive that from
$scfg->{content}->{backup} below already, that can only get set when on a
storage that declares to support backups, and actually works for external
ttorage plugins too.

>      die "can't use storage '$storage' for backups - wrong content type\n"
>  	if (!$scfg->{content}->{backup});
>  
> 





      reply	other threads:[~2021-07-19 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 11:58 Oguz Bektas
2021-07-19 12:57 ` Thomas Lamprecht [this message]

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=15a01769-c3b9-5b20-b9cb-62ca8c1fb3a1@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=o.bektas@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