Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 128 #200

Merged
merged 2 commits into from
Apr 4, 2025
Merged

Issue 128 #200

merged 2 commits into from
Apr 4, 2025

Conversation

BlackIkeEagle
Copy link
Member

@BlackIkeEagle BlackIkeEagle commented Apr 2, 2025

test + workaround for #128

Closes #128

Created a par2 set with parpar since par2cmdline normally should not
allow empty files to be included in the parset.

This test is currently failing because the test-a.data file is empty.

```
Repair is required.
1 file(s) exist but are damaged.
10 file(s) are ok.
You have 1029 out of 1029 data blocks available.
You have 52 recovery blocks available.
Repair is possible.
You have an excess of 52 recovery blocks.
None of the recovery blocks will be used for the repair.

Wrote 0 bytes to diska

Verifying repaired files:

Target: "test-a.data" - empty.
Repair Failed.
```

Tickets: #128
Signed-off-by: BlackEagle <[email protected]>
This is a workaround for empty files in a parset breaking repair.

The empty file will always land in the unverifiable sourcefile list.
But we can match it lateron. Currently I don't think we can get it in
the verifiedsourcefiles because there are a ton of guardrails against
loading 0 byte files.

It also looks on first glance this workaround is needed to be able to
verify parfiles created with other tools not skipping on 0 byte files.

Tickets: #128
Signed-off-by: BlackEagle <[email protected]>
@BlackIkeEagle BlackIkeEagle merged commit 5015e84 into master Apr 4, 2025
@BlackIkeEagle BlackIkeEagle deleted the issue-128 branch April 7, 2025 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problem with empty (0 Bytes) files.
1 participant