File is being copied even though it's too large for underlying filesystem

[tobihagemann]

Description

Beginning of a file is being copied even though the whole file is too large for underlying filesystem.

System Setup

• Operating system and version: macOS 10.15.6
• Cryptomator version: 1.5.6
• Volume type: FUSE/WebDAV

Steps to Reproduce

1. Ideally, have a FAT32-formatted filesystem (e.g., USB drive) that has more than 4 GiB free space.
2. Create and unlock a vault inside that filesystem.
3. Copy a >4 GiB file into the vault.

Expected Behavior

I would expect an error message that the file cannot be copied because it's too large for the filesystem's format.

Actual Behavior

File is being copied without any errors. It even tries to copy the part that comes after the 4 GiB and doesn't fail there either. In the end, you have a roughly 4 GiB file in the vault that's corrupt.

Reproducibility

Always

[overheadhunter]

Well we can't show an error when beginning to write. We have to rely on the underlying file system to throw an I/O error when reaching the limit.

Can you do some tests within jshell? Just copy 5GiB of 0x00 to a file located on such a FAT drive and see what gets thrown.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.