The problem is FUSE together with backup of a running container. It is explained in the documentation
https://pve.proxmox.com/pve-docs/chapter-pct.html#_fuse_mounts The solution that is proposed in that link worked for me for GlusterFS. On Fri, Dec 11, 2020 at 11:13:46AM +0100, Bertorello, Marco wrote: > Here the lxc configuration (a try to backup is currently running): > > root@pve3:~# cat /etc/pve/lxc/120.conf > arch: amd64 > cores: 1 > features: fuse=1,nesting=1 > hostname: haproxy3 > lock: snapshot > memory: 1024 > net0: > name=eth0,bridge=vmbr0,gw=192.168.1.1,hwaddr=62:FF:14:9F:F8:A6,ip=192.168.1.53/24,type=veth > ostype: debian > rootfs: DS1:subvol-120-disk-0,size=8G > swap: 512 > > [vzdump] > #vzdump backup snapshot > arch: amd64 > cores: 1 > features: fuse=1,nesting=1 > hostname: haproxy3 > memory: 1024 > net0: > name=eth0,bridge=vmbr0,gw=192.168.1.1,hwaddr=62:FF:14:9F:F8:A6,ip=192.168.1.53/24,type=veth > ostype: debian > rootfs: DS1:subvol-120-disk-0,size=8G > snapstate: prepare > snaptime: 1607674369 > > swap: 512 > _______________________________________________ pve-user mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
