fix: Truncated fat entries on error

[ikrivosheev]

Closed: #41

[mdsteele]

Looks like this needs some test updates.

[ikrivosheev]

@ideeockus thank you for the help!
@mdsteele could you review?)

[mdsteele]

I'm a little confused what's going on with this change. Seems like it's changing to ignore IO errors? Why is that desired?

[ideeockus]

@mdsteele fat entries may be incomplete. read_exact emits Error { kind: UnexpectedEof, message: "failed to fill whole buffer" } in case of incomplete data

[mdsteele]

Thanks, and sorry for the slow replies on my part. Could we add a unit test for this? It would be good to have. Also, I guess I'm concerned that this might not be the best way to solve the problem (I'm worried it will cover up other kinds of errors that it shouldn't), but having something to test against will make it easier to try out alternative solutions in the future.

[sftse]

This is at least partially superseeded by #65 and #71. There are still cases that could lead to a mismatch in the FAT and the actual number of sectors, in which case we could simply truncate the FAT. The original issue #41 prompting this however seems to have been fixed.

[ikrivosheev]

This is at least partially superseeded by #65 and #71. There are still cases that could lead to a mismatch in the FAT and the actual number of sectors, in which case we could simply truncate the FAT. The original issue #41 prompting this however seems to have been fixed.

Thank you! I'll close the PR.