proxmox-backup-client: mounting a pxar archive gives truncated files

R

resoli

Renowned Member
Mar 9, 2010
147
4
83
I backup a filesystem tree inside a vm, then using proxmox-backup-client mount i tried to compare the original tree with the mounted backup.

The filesystem I mounted is the content of a virtio .iso (virtio-win-0.1.221.iso).
  • Original tree: /opt/restore/bigfs/virtio-win-0.1.221/
  • Mounted backup: /tmp/backup/bigfs/virtio-win-0.1.221/
Code: 
# sha256sum /tmp/backup/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe
5c3ce2eb7611b2089b5b847f01c3ddf43143f0f4ebce5e4f757c22c792edf848  /tmp/backup/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe

Code: 
# sha256sum /opt/restore/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe
4e16b57aab0206093d891e109e4e94f09f1300552e5339a23816540ce598a855  /opt/restore/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe

The file is truncated at 0x000bd566
Code: 
# hd /tmp/backup/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe | tail
000bd4e0  aa 05 aa 03 aa 07 6a 00  6a 04 6a 02 6a 06 6a 01  |......j.j.j.j.j.|
000bd4f0  6a 05 6a 03 6a 07 ea 00  ea 04 ea 02 ea 06 ea 01  |j.j.j...........|
000bd500  ea 05 ea 03 ea 07 1a 00  fa 07 34 08 34 04 34 0c  |..........4.4.4.|
000bd510  34 02 34 0a 34 06 34 0e  34 01 34 09 34 05 34 0d  |4.4.4.4.4.4.4.4.|
000bd520  34 03 34 0b 34 07 34 0f  b4 00 b4 08 b4 04 b4 0c  |4.4.4.4.........|
000bd530  b4 02 b4 0a b4 06 b4 0e  b4 01 b4 09 b4 05 b4 0d  |................|
000bd540  b4 03 b4 0b b4 07 b4 0f  74 00 74 08 74 04 74 0c  |........t.t.t.t.|
000bd550  74 02 74 0a 74 06 74 0e  74 01 74 09 74 05 74 0d  |t.t.t.t.t.t.t.t.|
000bd560  74 03 74 0b 74 07 74                              |t.t.t.t|
000bd567

Code: 
# hd -s 0x000bd4e0 -n 160 /opt/restore/bigfs/virtio-win-0.1.221/virtio-win-guest-tools.exe
000bd4e0  aa 05 aa 03 aa 07 6a 00  6a 04 6a 02 6a 06 6a 01  |......j.j.j.j.j.|
000bd4f0  6a 05 6a 03 6a 07 ea 00  ea 04 ea 02 ea 06 ea 01  |j.j.j...........|
000bd500  ea 05 ea 03 ea 07 1a 00  fa 07 34 08 34 04 34 0c  |..........4.4.4.|
000bd510  34 02 34 0a 34 06 34 0e  34 01 34 09 34 05 34 0d  |4.4.4.4.4.4.4.4.|
000bd520  34 03 34 0b 34 07 34 0f  b4 00 b4 08 b4 04 b4 0c  |4.4.4.4.........|
000bd530  b4 02 b4 0a b4 06 b4 0e  b4 01 b4 09 b4 05 b4 0d  |................|
000bd540  b4 03 b4 0b b4 07 b4 0f  74 00 74 08 74 04 74 0c  |........t.t.t.t.|
000bd550  74 02 74 0a 74 06 74 0e  74 01 74 09 74 05 74 0d  |t.t.t.t.t.t.t.t.|
000bd560  74 03 74 0b 74 07 74 0f  f4 00 f4 08 f4 04 f4 0c  |t.t.t.t.........|
000bd570  04 00 7a 01 7a 05 7a 03  7a 07 fa 00 fa 04 fa 02  |..z.z.z.z.......|
000bd580

Small files are not truncated.

Complete restores and partial restores done with proxmox-backup-client catalog shell (but see this other post ) are ok.
 
Last edited:
resoli said:
I backup a filesystem tree inside a vm, then using proxmox-backup-client mount i tried to compare the original tree with the mounted backup.
Click to expand...
which filesystem do you use in the vm? and which versions of the proxmox-backup-client (when backing up & restoring) ?
 
The vm is debian 11
Filesystem on vm: ext4
proxmox-backup-client package version (from dpkg -l): 2.2.5-1 - repo: pve-no-subscription
Code: 
# proxmox-backup-client version
client version: 2.2.5
 
I have tried to switch my repo to Proxmox Backup Client Repository

APT-based Proxmox Backup Client Repository​

For modern Linux distributions using apt as package manager, like all Debian and Ubuntu Derivative do, you may be able to use the APT-based repository.
In order to configure this repository you need to first setup the Proxmox release key. After that, add the repository URL to the APT sources lists.
Click to expand...
... which resulted in a downgrade to client version: 2.2.1

No difference.

I tried the .pxar mount with client version: 2.2.4 (pve enterprise repository) on a pve node; same behaviour.
 
Last edited:
(EDIT: it seems indeed file truncation ...)
I've indagated furthermore, and what seemed file truncation is a file corruption, unrelated to file size (probably big files have more chances to be read as corrupted).


Bash: 
# find virtio-win-0.1.221 -size +8M | while read f; do diff -qr {/opt/restore,/tmp/backup}/bigfs/${f} > /dev/null && echo -n "nodiff " || echo -n "diff "; ls -hs $f ; done
diff 9,1M virtio-win-0.1.221/guest-agent/qemu-ga-i386.msi
diff 9,2M virtio-win-0.1.221/guest-agent/qemu-ga-x86_64.msi
diff 30M virtio-win-0.1.221/virtio-win-guest-tools.exe
diff 11M virtio-win-0.1.221/NetKVM/2k12R2/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w8/amd64/netkvmco.pdb
nodiff 11M virtio-win-0.1.221/NetKVM/w8/x86/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/2k22/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w8.1/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w8.1/x86/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/2k19/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w11/ARM64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w11/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/2k16/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/2k12/amd64/netkvmco.pdb
diff 9,5M virtio-win-0.1.221/NetKVM/2k8/amd64/netkvmco.pdb
diff 9,4M virtio-win-0.1.221/NetKVM/2k8/x86/netkvmco.pdb
diff 12M virtio-win-0.1.221/NetKVM/2k8R2/amd64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w10/ARM64/netkvmco.pdb
diff 11M virtio-win-0.1.221/NetKVM/w10/amd64/netkvmco.pdb
nodiff 11M virtio-win-0.1.221/NetKVM/w10/x86/netkvmco.pdb
diff 12M virtio-win-0.1.221/NetKVM/w7/amd64/netkvmco.pdb
diff 12M virtio-win-0.1.221/NetKVM/w7/x86/netkvmco.pdb
 
Last edited:
ok i can reproduce that, AFAICS this is only a problem with the 'mount' command, normal restore should work fine.
i'll look into it...
 
hi, i have the same problem (debian10.13+proxmox-backup-client 1.1.14+pbs2.1-1), seems to be always the same files, event if path is different
it's a very frightening error, i hope i didn't lost data
any news about a corrected version ?
 
pvelover said:
hi, i have the same problem (debian10.13+proxmox-backup-client 1.1.14+pbs2.1-1), seems to be always the same files, event if path is different
it's a very frightening error, i hope i didn't lost data
any news about a corrected version ?
Click to expand...
the fix is already in the current supporte pbs 2.x releases
and pbs 1.0 is eol, as is debian 10 already (see https://wiki.debian.org/DebianReleases)

so i'd recommend upgrading both your debian machine as well as the backup client
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back