On 5/4/25 3:53 PM, ToddAndMargo via users wrote:
Hi All,
I have two servers affected by:
restore: <name unknown>: ftruncate: Invalid argument
https://bugzilla.redhat.com/show_bug.cgi?id=2359295
This is pretty critical to me. And pretty much anyone
using dump/restore. The maintainer seems to be ignoring
this.
Is there an ext4 sub for dump/restore that is maintained by
the repo?
Many thanks,
-T
Follow up. dump/restore has been fixed.
With borg, I backed up three file and restored
them (somewhere else).
Originals:
$ dd count=0 bs=1M seek=100 of=sparseFile
$ du --bytes KVM-W10.raw KVM-W11.raw sparseFile
64_424_509_440 KVM-W10.raw
133_143_986_176 KVM-W11.raw
104_857_600 sparseFile
$ du --block-size=1 KVM-W10.raw KVM-W11.raw sparseFile
48_891_629_568 KVM-W10.raw
51_850_604_544 KVM-W11.raw
0 sparseFile
$ sha256sum KVM-W10.raw KVM-W11.raw sparseFile
67965ba41959f8e43df5710bfb9f8e95f741b89ead48c94a2206d786e80d23cc
/home/kvm/KVM-W10.raw
0b25189cdd77f9b9bbe663e06b73916ff9cce27f2c430358910977c062dfa8ba
KVM-W11.raw
20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e
sparseFile
Recovered files:
# du --block-size=1 /home/temp/borg/*
64_424_521_728 /home/temp/borg/KVM-W10.raw
133_144_117_248 /home/temp/borg/KVM-W11.raw
104_857_600 /home/temp/borg/sparseFile
# sha256sum /home/temp/borg/*
67965ba41959f8e43df5710bfb9f8e95f741b89ead48c94a2206d786e80d23cc
/home/temp/borg/KVM-W10.raw
0b25189cdd77f9b9bbe663e06b73916ff9cce27f2c430358910977c062dfa8ba
/home/temp/borg/KVM-W11.raw
20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e
/home/temp/borg/sparseFile
So the checksum was equivalent, but I lost my sparseness.
As a test, now that dump/restore is working again, I backed up
a sparse file and restored:
Sparse file backups and restored with dump/restore:
# du --bytes *
104857600 sparseFile
104857600 sparseFile.orig
# du --block-size=1 *
0 sparseFile
0 sparseFile.orig
# sha256sum *
20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e sparseFile
20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e
sparseFile.orig
dump/restore gives back exactly what it backed up. Exactly.
Borg is incapable of the same result. And I am backing up
a lot of qamu-kvm virtual drives. They are sparse files and
large. If borg can not deal with sparse files, then it is not
a good candidate for replacing dump/restore. Bord
will give back equivalent files but they will be much larger,
wasting a lot of drive space..
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
