"tar: write error" during a Restore

bread-baker

Member
Mar 6, 2010
432
0
16
Hello,
restoring a kvm this displays:
Code:
extracting archive '/var/lib/vz/dump/vzdump-qemu-100-2012_05_01-10_52_28.tar.lzo'
extracting 'qemu-server.conf' from archive
extracting 'vm-disk-ide0.raw' from archive
  Rounding up size to full physical extent 4.00 GiB
  Logical volume "vm-103-disk-1" created
new volume ID is 'drbd-fbc241:vm-103-disk-1'
restore data to '/dev/drbd-fbc241/vm-103-disk-1' (4294967296 bytes)
97+3329501 records in
16384+0 records out
4294967296 bytes (4.3 GB) copied, 138.969 s, 30.9 MB/s
extracting 'vm-disk-scsi0.raw' from archive
  Rounding up size to full physical extent 120.00 GiB
  Logical volume "vm-103-disk-2" created
new volume ID is 'drbd-fbc241:vm-103-disk-2'
restore data to '/dev/drbd-fbc241/vm-103-disk-2' (128849018880 bytes)
tar: write error

Now I remember from before that the restore should work. Still that is a 110GB disk getting restored and that last line will stay there a while. so check at cli that the restore is still in progress:
Code:
ps -ef | grep vzdump  | grep -v grep 


root      468621  468616  0 11:17 ?        00:00:00 sh -c zcat -f|tar xf /var/lib/vz/dump/vzdump-qemu-100-2012_05_01-10_52_28.tar.lzo '--to-command=/usr/lib/qemu-server/qmextract --storage drbd-fbc241'
root      468623  468621 22 11:17 ?        00:10:24 tar xf /var/lib/vz/dump/vzdump-qemu-100-2012_05_01-10_52_28.tar.lzo --to-command=/usr/lib/qemu-server/qmextract --storage drbd-fbc241

Now in the past the restore would work. It has been in progress for more then 30 minutes... so I'll post result later.
 
the restore ended up working:
Code:
tar: write error
4122+93066018 records in
491520+0 records out
128849018880 bytes (129 GB) copied, 4299.35 s, 30.0 MB/s
TASK OK
 
i got a similar issue at my first kvm (1.x -> 2.1) restore... the task ended with OK but...
what "error" it is? have you found? there is something we should do or it is expected?
:confused:
Marco
 
Hello Marco

There is nothing to do or worry about when that message displays [ that conclusion is from reading threads on this forum and mails from the pve-user mail list. ] . It looks like one of those tar errors that should be a warning. my guess is that the devs will get to dealing with this issue later.
 
hi, thanks.
I agree, i got that a few times (can't say why) but in the end the TASK was ok and that "tar error" had no relation to possible problems starting or running the machine...

Marco
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!