Skip to content
This repository has been archived by the owner on Oct 10, 2022. It is now read-only.

Silent Data Corruption Still Occurs Occasionally #33

Closed
DavidBerdik opened this issue Mar 24, 2020 · 7 comments
Closed

Silent Data Corruption Still Occurs Occasionally #33

DavidBerdik opened this issue Mar 24, 2020 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@DavidBerdik
Copy link
Owner

Apparently, there is still an issue with data corruption occurring intermittently when using InfiniDrive. Further investigation in to this is necessary.

It was previously thought that this issue had been resolved, however, further testing has revealed additional occurrences of such corruption.

@DavidBerdik DavidBerdik added the bug Something isn't working label Mar 24, 2020
@DavidBerdik DavidBerdik self-assigned this Apr 5, 2020
@DavidBerdik DavidBerdik reopened this Apr 6, 2020
@DavidBerdik
Copy link
Owner Author

The following 6 Word documents were manually located and downloaded from a 50GB InfiniDrive upload that was known to be corrupted with 3 duplicates. Both versions of the 3 occurring duplicates are attached. Note that the first two duplicates appear to be merely copies of the same data, but the second file in the third pair of duplicates appears to be corrupted.

Duplicate Set 1

Duplicate Set 2

Duplicate Set 3

@DavidBerdik
Copy link
Owner Author

b0275cc is expected to resolve this issue. This patch is currently undergoing testing.

@DavidBerdik
Copy link
Owner Author

b0275cc did not resolve the issue. cdc632c is a redesign of the corruption detection and repair system that is currently in testing.

@DavidBerdik
Copy link
Owner Author

Testing of uploads using the cdc632c redesign suggests that the issue has been properly addressed. To ensure this, download tests are currently being performed. If the resulting files are properly restored, this issue will be marked as closed and the fix will be released as v1.0.16.

@DavidBerdik
Copy link
Owner Author

When performing download testing, an additional edge case was discovered. File corruption occasionally occurs in the form of a 1x1 image. The following is a sample fragment which demonstrates this.

162.docx

@DavidBerdik
Copy link
Owner Author

5d47d87 attempts to patch the aforementioned edge case. This patch is currently being tested.

@DavidBerdik
Copy link
Owner Author

The introduction of CRC32 hashing to verify fragments successfully resolved this problem. As of v1.0.16, there are no known ways for corruption to occur and remain undetected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant