No space left on device

S

SamTzu

Renowned Member
Mar 27, 2009
527
17
83
Helsinki, Finland
sami.mattila.eu
No matter how I try I can't seem to restore one image. It always complains space even when I have tried to restore it to multiple devices that all work fine and have more than enough space left (+1TB.) The image it self is only 12Gb in size.

Code: 
Formatting '/mnt/pve/Q1SATA/images/401/vm-401-disk-1.raw', fmt=raw size=12884901888
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 3145728 4k blocks and 786432 inodes
Filesystem UUID: f1a6bbcb-57cf-4781-824d-6ff0b8d4b658
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: 0/96 done
Writing inode tables: 0/96 done
Creating journal (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/96 done

extracting archive '/mnt/pve/Q1Backup/dump/vzdump-openvz-401-2016_08_15-18_03_23.tar.lzo'
tar: ./var/cache/apt-cacher-ng/download.webmin.com/download/repository/pool/contrib/w/webmin/webmin_1.791_all.deb: Cannot write: No space left on device
tar: Skipping to next header
tar: ./var/cache/apt-cacher-ng/download.webmin.com/download/repository/pool/contrib/w/webmin/webmin_1.720: Cannot write: No space left on device
tar: ./var/cache/apt-cacher-ng/download.webmin.com/download/repository/pool/contrib/w/webmin/webmin_1.730_all.deb.head: Cannot write: No space left on device
tar: ./var/cache/apt-cacher-ng/download.webmin.com/download/repository/pool/contrib/w/webmin/webmin_1.770_all.deb.head: Cannot write: No space left on device
tar: ./var/cache/apt-cacher-ng/download.webmin.com/download/repository/pool/contrib/w/webmin/webmin_1.801_all.deb.head: Cannot write: No space left on device
 
SamTzu said:
That VM is no more. This is about upgrading Proxmox to use LXC instead of OpenVZ. Unfortunately it seems that I have to create Proxmox 3 on KVM to run that old OpenVZ VM on it.
Click to expand...

your backup archive contains more data than the automatically allocated space when restoring (this can happen when the information in the backed up configuration is wrong, for example because you also backed up network shares or other "extra" mounts). you can use the advanced mode of "pct restore" to specify the storage and size for the rootfs ("pct restore ID BACKUPARCHIVE -rootfs STORAGE:SIZEINGB [... other options ...]", see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_backup_and_restore).
 
You must log in or register to reply here.
Top Bottom