This is a continuation of the thread on restoring backups of vm's with large multiple disks. I believe the cause of the "tar: write error" was due to the system root disk being smaller than the vm disks being restored (restored to the 2nd "image" disk - very large).
Our server with Proxmox 2.1 has a 67Gb RAID1 system root disk /dev/sda (the /dev/sdb RAID5 image disk > 2Tb). The failing vm restore has a disk > 125Gb. As a test, i put the backup file on our older server with Proxmox 1.9. It has a 160Gb /dev/sda system root disk. The restore went fine with no errors. My hypothesis is i need to give our new server with Proxmox 2.1 a larger system root disk. I am surmising that the decompression process somehow uses the system root disk as a staging area before creating the final vm file on the image disk LVM.
My question is: Is it possible to remove/replace the smaller /dev/sda system root disk with larger drives and then rebuild the system WITHOUT loosing all my vm's stored on the /dev/sdb image disk LVM file system? Any recommendations on how to do this with minimal down time would be very welcome.
root@proxmox2a:~# pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name ImageDisk
PV Size 2.27 TiB / not usable 0
Allocatable yes
PE Size 4.00 MiB
Total PE 594853
Free PE 211094
Allocated PE 383759
PV UUID Rr7H0n-iTMo-X4w3-2bXK-2dST-HQHn-4YcQMS
--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV Size 66.55 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 17037
Free PE 2143
Allocated PE 14894
PV UUID mMDAqX-amB7-HVBM-huez-GqTm-PmV5-GbYaR0
root@proxmox2a:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 17G 1.4G 15G 9% /
tmpfs 18G 0 18G 0% /lib/init/rw
udev 18G 332K 18G 1% /dev
tmpfs 18G 19M 18G 1% /dev/shm
/dev/mapper/pve-data 33G 24G 8.6G 74% /var/lib/vz
/dev/sda1 495M 56M 415M 12% /boot
/dev/fuse 30M 16K 30M 1% /etc/pve
root@proxmox2a:~# vgdisplay
--- Volume group ---
VG Name ImageDisk
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 158
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 17
Open LV 14
Max PV 0
Cur PV 1
Act PV 1
VG Size 2.27 TiB
PE Size 4.00 MiB
Total PE 594853
Alloc PE / Size 383759 / 1.46 TiB
Free PE / Size 211094 / 824.59 GiB
VG UUID jpHHoE-GcH8-Y9Op-nEkn-nqvo-ecVm-UHHmPN
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 12
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 66.55 GiB
PE Size 4.00 MiB
Total PE 17037
Alloc PE / Size 14894 / 58.18 GiB
Free PE / Size 2143 / 8.37 GiB
VG UUID UJZIG3-GP2q-r0vG-M1cd-H125-Qnyi-dZG4fq
Our server with Proxmox 2.1 has a 67Gb RAID1 system root disk /dev/sda (the /dev/sdb RAID5 image disk > 2Tb). The failing vm restore has a disk > 125Gb. As a test, i put the backup file on our older server with Proxmox 1.9. It has a 160Gb /dev/sda system root disk. The restore went fine with no errors. My hypothesis is i need to give our new server with Proxmox 2.1 a larger system root disk. I am surmising that the decompression process somehow uses the system root disk as a staging area before creating the final vm file on the image disk LVM.
My question is: Is it possible to remove/replace the smaller /dev/sda system root disk with larger drives and then rebuild the system WITHOUT loosing all my vm's stored on the /dev/sdb image disk LVM file system? Any recommendations on how to do this with minimal down time would be very welcome.
root@proxmox2a:~# pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name ImageDisk
PV Size 2.27 TiB / not usable 0
Allocatable yes
PE Size 4.00 MiB
Total PE 594853
Free PE 211094
Allocated PE 383759
PV UUID Rr7H0n-iTMo-X4w3-2bXK-2dST-HQHn-4YcQMS
--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV Size 66.55 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 17037
Free PE 2143
Allocated PE 14894
PV UUID mMDAqX-amB7-HVBM-huez-GqTm-PmV5-GbYaR0
root@proxmox2a:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 17G 1.4G 15G 9% /
tmpfs 18G 0 18G 0% /lib/init/rw
udev 18G 332K 18G 1% /dev
tmpfs 18G 19M 18G 1% /dev/shm
/dev/mapper/pve-data 33G 24G 8.6G 74% /var/lib/vz
/dev/sda1 495M 56M 415M 12% /boot
/dev/fuse 30M 16K 30M 1% /etc/pve
root@proxmox2a:~# vgdisplay
--- Volume group ---
VG Name ImageDisk
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 158
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 17
Open LV 14
Max PV 0
Cur PV 1
Act PV 1
VG Size 2.27 TiB
PE Size 4.00 MiB
Total PE 594853
Alloc PE / Size 383759 / 1.46 TiB
Free PE / Size 211094 / 824.59 GiB
VG UUID jpHHoE-GcH8-Y9Op-nEkn-nqvo-ecVm-UHHmPN
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 12
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 66.55 GiB
PE Size 4.00 MiB
Total PE 17037
Alloc PE / Size 14894 / 58.18 GiB
Free PE / Size 2143 / 8.37 GiB
VG UUID UJZIG3-GP2q-r0vG-M1cd-H125-Qnyi-dZG4fq