[pve-devel] [PATCH manager] Allow tmpfs for vzdump temporary files

2017-07-23 Thread Martin Lablans
Dear all,

allowing vzdump to use ram-backed directory for temporary backup files 
speeds up backups and thus results in shorter container/VM downtimes.
Currently, VZDump.pm will decline tmpfs-backed directories as they are
are missing from its hardcoded POSIX compliant filesystem list.

This small patch will add tmpfs to vzdump's list of POSIX compliant
filesystems and thus enable it for use in vzdump backups.

Kind regards,
Martin

Martin Lablans (1):
  Allow vzdump to use tmpfs for temporary files.

 PVE/VZDump.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.1.4

___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] [PATCH manager] Allow tmpfs for vzdump temporary files

2017-07-23 Thread Andreas Steinel
For simple container/systems is is probably OK, but I cannot backup a
multiple TB system on tmpfs.

Also, the backup is normally limited by CPU power or network
throughput, not storage speed (at least for my machines).

On Sun, Jul 23, 2017 at 7:40 PM, Martin Lablans  wrote:
> Dear all,
>
> allowing vzdump to use ram-backed directory for temporary backup files
> speeds up backups and thus results in shorter container/VM downtimes.
> Currently, VZDump.pm will decline tmpfs-backed directories as they are
> are missing from its hardcoded POSIX compliant filesystem list.
>
> This small patch will add tmpfs to vzdump's list of POSIX compliant
> filesystems and thus enable it for use in vzdump backups.
>
> Kind regards,
> Martin
>
> Martin Lablans (1):
>   Allow vzdump to use tmpfs for temporary files.
>
>  PVE/VZDump.pm | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.1.4
>
> ___
> pve-devel mailing list
> pve-devel@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel