Recent content by spq

When backup takes more than 24 hours and then fails I would be happy to have at least something ... :D

I can't think of a name pattern, because it's randomly generated name. I only can distinguish file by its size being 0. I just wondered why pbs client fails whole backup when encountering such file and if it's possible to make it to continue on such encounter.

I also think it's related to gluster. When I execute getfattr on bad file, I get getfattr: /path/to/file: No such attribute I also noticed, that I can't copy file, I get error: No data available but I can remove and rsync that file. Additional info: Client - CentOS 7.9.2009 Gluster - 6.0-37.el7...

I have application running on gluster storage, sometimes, for various reasons, empty files are created on this storage (they might be locked by some process). When proxmox-backup-client encounters such file whole backup fails with error: Error: error at "/path/to/file": failed to read xattrs...