PVE-PBS error restoring CT

U

Uncertainty

Member
Nov 22, 2021
5
0
6
33
Good afternoon!
There was a problem while restoring CT with proxmox backup server. The recovery process lasts about an hour, at the end of which the error

Code: 
"Error: error extracting archive - error at entry "root": failed to copy file contents: No space left on device (os error 28)"

However, there is space available. In the task logs on PBS there is this:

Code: 
"TASK ERROR: connection error: connection reset"
In which direction to dig, where to look?

I tried backups of various days, the problem is with everyone. Recovery of other CTs and VMs is successful, the problem is only with one single CT.

On my last trying - log on PBS

Code: 
2022-09-01T15:51:24+12:00: reader finished successfully
2022-09-01T15:51:24+12:00: TASK OK
But task error:

Code: 
Error: error extracting archive - error at entry "root": failed to copy file contents: No space left on device (os error 28)
TASK ERROR: unable to restore CT 102 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/102/2022-08-28T10:30:29Z root.pxar /var/lib/lxc/102/rootfs --allow-existing-dirs --repository backup@pbs@xx.xx.xx.xx:backup' failed: exit code 255




Versions: PVE - 7.2-7 , 3 nodes per cluster
PBS-2.2-5 (virtual machine)

I apologize in advance for English, it's not my main language.
 
Last edited:
Uncertainty said:
However, there is space available. In the task logs on PBS there is this:
Click to expand...
The PBS error seems to be a followup one from the client suddenly disconnecting after triggering the "ENOSPACE" error.

How did you check that there's indeed enough space? Does df -h during restore show a filesystem mount growing in usage? As after the error the partially restored files should be already cleaned up, so the out-of-space situation wouldn't be there anymore.
 
t.lamprecht said:
The PBS error seems to be a followup one from the client suddenly disconnecting after triggering the "ENOSPACE" error.

How did you check that there's indeed enough space? Does df -h during restore show a filesystem mount growing in usage? As after the error the partially restored files should be already cleaned up, so the out-of-space situation wouldn't be there anymore.
Click to expand...
thanks for answer , this CT is successful restored, but i dont know how : )

df -h - is ok, free space available.
 
You must log in or register to reply here.
Top Bottom