Running kup with the recent versions of Plasma and OpenSuse Tumbleweed I noticed that kup successfully checks the file consistency but before completing the saving of the backup it runs into an error with the following message:
Kup did not successfully complete the bup backup job: failed to generate recovery info.
The log file says:
bup “-d” “/run/media/peter/697dab13-1f0f-4cac-b143-708efd90520b/vision_01” “fsck” “-g” “-j” “4” You must specify a list of files when creating. b’pack-11a531ccfdc81e75d0a8bdce0ccb6f020604dc12’ par2 create: failed (3) You must specify a list of files when creating. b’pack-fd1a5ade3f8e6ee875ddf241e7d45497f8d89ef1’ par2 create: failed (3) You must specify a list of files when creating. b’pack-2bbe5ca7bead405d5aed6337b02d9d1dbc80ca55’ par2 create: failed (3) You must specify a list of files when creating. b’pack-085799cc7db6c29b46c24f9d4be1537554b4d040’ par2 create: failed (3) You must specify a list of files when creating. b’pack-4cdcb44fbfedf2a0bddc260c6d11e663ea0cd38c’ par2 create: failed (3) You must specify a list of files when creating. b’pack-814fcf46861d2792631bc44f1e4eb794566b9475’ par2 create: failed (3)
So, how can I find out which files are causing the issue in order to fix the problem?
I experience exactly the same issue. It came with some update of Tumbleweed, unfortunately, I do not recall when. The last successful update was on September 25. I have not changed the configuration. In my case, it’s a versioned backup with my complete home directory as source, destination is an external SSD, schedule is active usage time of 6 hours with confirmation before saving the backup. In the advanced options, show hidden folders, verify integrity, and generate recovery information are activated and no files are excluded.
fsck: No filenames given: checking all packs.
fsck: checking b'pack-56dc0af95580c945fd648fae880fa815976e87b5' (par2)
Assuming par2 supports parallel processing
pack-56dc0af95580c945fd648fae880fa815976e87b5 ok
fsck: checking b'pack-52a1c8acc71413727963a2e225f1b1fe8ea465e3' (par2)
pack-52a1c8acc71413727963a2e225f1b1fe8ea465e3 ok
fsck: checking b'pack-a55ca60b16f1a5b183a488479aa2427d002927ca' (par2)
pack-a55ca60b16f1a5b183a488479aa2427d002927ca ok
...
and on and on like this, until
fsck done.
[...]
fsck: checking b'pack-57dbb4c6e6eafd944b4ede61de841f47383e27a2' (par2)
pack-57dbb4c6e6eafd944b4ede61de841f47383e27a2 ok
fsck: checking b'pack-f15eae9dcb8b08db246c4c15e26e41de8cb122d7' (par2)
pack-f15eae9dcb8b08db246c4c15e26e41de8cb122d7 ok
fsck: checking b'pack-ae68d0660bd99fc7b182610726e2a8299c722a5c' (par2)
pack-ae68d0660bd99fc7b182610726e2a8299c722a5c ok
fsck: checking b'pack-ba4b29b5e5b54a7059aa88c67aa2f62c73a782e1' (git)
You must specify a list of files when creating.
b'pack-ba4b29b5e5b54a7059aa88c67aa2f62c73a782e1' par2 create: failed (3)
fsck: checking b'pack-62af47bbdc005036cb2a256cb327572ec08cbd6b' (git)
pack-ba4b29b5e5b54a7059aa88c67aa2f62c73a782e1 failed
You must specify a list of files when creating.
b'pack-62af47bbdc005036cb2a256cb327572ec08cbd6b' par2 create: failed (3)
pack-62af47bbdc005036cb2a256cb327572ec08cbd6b failed
fsck: checking b'pack-4f7578d9ef0c08ad9adc0406af8a59658810c069' (git)
You must specify a list of files when creating.
b'pack-4f7578d9ef0c08ad9adc0406af8a59658810c069' par2 create: failed (3)
pack-4f7578d9ef0c08ad9adc0406af8a59658810c069 failed
fsck: checking b'pack-cdf78d56db5ecda26cb5056a62c261f7a168bd29' (git)
You must specify a list of files when creating.
b'pack-cdf78d56db5ecda26cb5056a62c261f7a168bd29' par2 create: failed (3)
pack-cdf78d56db5ecda26cb5056a62c261f7a168bd29 failed
fsck: checking b'pack-0a9adcc81de68c9ede1a14c320505d9cc7021517' (git)
You must specify a list of files when creating.
b'pack-0a9adcc81de68c9ede1a14c320505d9cc7021517' par2 create: failed (3)
pack-0a9adcc81de68c9ede1a14c320505d9cc7021517 failed
fsck: checking b'pack-22c433ebf0e774182f3f2d7d723aede088850888' (git)
You must specify a list of files when creating.
b'pack-22c433ebf0e774182f3f2d7d723aede088850888' par2 create: failed (3)
fsck done.
pack-22c433ebf0e774182f3f2d7d723aede088850888 failed
I guess that something changed for the backups after September 25, perhaps with an update of kup, bup, or par2cmdline.
The destination path was correct. couldn`t findout whathe problem was, so I created a new backup plan and everything is working fine again. Thanks for your support anyway.