[SOLVED] Restoring a container leads to error: "Cannot write: No space left on device"

[miracuru]

Hi

I have a new server, where I just installed proxmox.
I have two SSD installed but it seems it doesn't matter, which one I take to restore a container on it.
I have only issues with this container. All others have worked.

This is what I have from `df -h /var/tmp`
```bash
df -h /var/tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 94G 24G 66G 27% /
```

```bash
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 1.7M 3.2G 1% /run
/dev/mapper/pve-root 94G 24G 66G 27% /
tmpfs 16G 43M 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 192K 127K 61K 68% /sys/firmware/efi/efivars
/dev/nvme0n1p2 1022M 12M 1011M 2% /boot/efi
/dev/fuse 128M 16K 128M 1% /etc/pve
tmpfs 3.2G 0 3.2G 0% /run/user/0
```

From storage:



What could be the issue here?
If further information about my system is needed, please let me know.



This is the log, which appears, when I try to restore the container (the errors continue to a few hundred or thousand lines with everytime the same errors):

recovering backed-up configuration from 'local:backup/vzdump-lxc-103-2024_04_15-19_44_02.tar.zst'
Wiping ext4 signature on /dev/SamsungEVO/vm-100-disk-0.
Logical volume "vm-100-disk-0" created.
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 6791dcbc-d2c9-41e5-80d4-6b9e5dc45550
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
restoring 'local:backup/vzdump-lxc-103-2024_04_15-19_44_02.tar.zst' now..
extracting archive '/var/lib/vz/dump/vzdump-lxc-103-2024_04_15-19_44_02.tar.zst'
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node: Cannot write: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/product.json: Cannot write: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/LICENSE: Cannot write: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/dist: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/dist/parse-proxy-response.d.ts.map: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/dist/index.js: Cannot open
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/dist/index.d.ts.map: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/dist/parse-proxy-response.js: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/https-proxy-agent/package.json: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-fs: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-fs/LICENSE: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-fs/package.json: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-fs/index.js: Cannot open
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/sandbox.js: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/package.json: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/index.js: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/headers.js: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/extract.js: Cannot open
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/LICENSE: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/tar-stream/pack.js: Cannot open
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/napi-build-utils: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/napi-build-utils/index.md: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/napi-build-utils/LICENSE: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/napi-build-utils/package.json: Cannot open: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/napi-build-utils/index.js: Cannot open
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/@microsoft: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules/@microsoft/1ds-post-js: Cannot mkdir: No such file or directory
tar: ./root/.vscode-server/cli/servers/Stable-863d2581ecda6849923a2118d93a088b0745d9d6/server/node_modules: Cannot mkdir: No space left on device

 

[Humay]

it creates 8GB filesystem? maybe filesystem was full on backup time?

try to increase volume size
https://forum.proxmox.com/threads/lxc-restore-no-space-left-on-device.82139/
also what size of backup?
do u restore to correct target? post ur datacenter->storage u need create like lvm-thin here
try mount NFS datastore (again use datacenter menu) and restore there

 

[miracuru]

Hi

Thanks for your replay.

This is my datacenter -> storage


I have tried to restore it to local-lvm and also to SamsungEVO. Both with the same result.
Checked the backup, which is 3.02GB when it is compress with .tar.zsd and took also a uncompressed backup, which is 9.51GB.

Thank you so much for the link. It describes exactly what I had. Last system was on ZSF. And as I heard, that ZFS isn't a good idea for consumer grade SSDs, so I went for the new server with ext4 file system. Therefore the difference in space.

I did now, what was described in the other post with manually changing the size with command: `pct restore --rootfs 16 104 /var/lib/vz/dump/vzdump-lxc-103-2024_04_16-00_01_04.tar --storage SamsungEVO` and this was a success this time.

Everything is working now.

Thank you so much.

 

[poweruser]

Hi,
I have the same situation and I am a bit confused. How does the fact that original host filesystem was compressed causes the error? From the guests perspective it has the same amount of space allocated is it not? There should be a reason that it's called transparent compression.
I just can't wrap my head around this.

If I check the backup configuration it says "rootfs: local-zfs:subvol-101-disk-0,size=8G", but running pct restore 101 /backup/vzdump-lxc-101-2024_09_27-05_10_54.tar.zst --rootfs 8 --storage local-lvm also throws the error about not enough space. Is 8G space after compression? What it represents?

Is there a way to check the uncompressed size of the backup file without extracting it from the zst file?

If you can clarify these points or point me to the relevant documentation it will be very helpful.