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

Certain filename disappears in Vault. #1961

Closed
2 tasks done
3735943886 opened this issue Dec 2, 2021 · 4 comments
Closed
2 tasks done

Certain filename disappears in Vault. #1961

3735943886 opened this issue Dec 2, 2021 · 4 comments
Assignees
Labels
misc:filesystem state:confirmed We are able to reproduce the reported behavior type:bug Something isn't working
Milestone

Comments

@3735943886
Copy link

3735943886 commented Dec 2, 2021

Please agree to the following

Summary

Certain filename disappears in Vault.

What software is involved?

  • Operating System: Windows 10, iOS 15.1
  • Cryptomator: 1.6.3(Windows) 1.6.1(iOS)
  • Vault is under OneDrive Business

Volume Type

Dokany

Steps to Reproduce

  1. Create document file named "Dynamic 18F-FPCIT PET Quantification of Parkinson Disease Metabolic Networks and Nigrostriatal Dopaminergic Dysfunction in a Single Imaging Session.docx" in Vault.
  2. Lock Vault and unlock again. (Or just wait some time without locking/unlocking vault)

Expected Behavior

The file should be there.

Actual Behavior

The file disappeared on both Windows and iOS client.
But when I tried recreating it (I tried with "copy con" in attached screenshot), it appeared again immediately.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

sc1
sc2

@3735943886 3735943886 added the type:bug Something isn't working label Dec 2, 2021
@overheadhunter
Copy link
Member

Since this is most likely length-related, can you please look up two values:

  1. If you open the vault.cryptomator file with a text editor and decode its contents (e.g. using jwt.io) (it doesn't contain secrets), there should be a value in the second block called "shorteningThreshold", which is usually 220. Can you confirm this?
  2. If you open %APPDATA%\Cryptomator\settings.json. For each vault you have, there is one block of data containing a value named maxCleartextFilenameLength. Can you tell us what this value is for the block that corresponds with your vault in question (you should be able to identify it using its path or displayName attribute)

@3735943886
Copy link
Author

Thank you for answer.

I checked and decoded the file vault.cryptomator, the value of "shorteningThreshold" was 220.
I do not know how to open %APPDATA%\Cryptomator\settings.json on iOS client, but "maxCleartextFilenameLength" was 2147483647 on Windows client.

Full path of problematic file was H:\personal_data\degree\2021-2\임상핵의학\Dynamic 18F-FPCIT PET Quantification of Parkinson Disease Metabolic Networks and Nigrostriatal Dopaminergic Dysfunction in a Single Imaging Session.docx and it was counted as 190 characters, however it might be longer bytes because it has some multibyte Korean characters in middle of path.

I tested long file name such as "aa.......aaa" and it also disappeared as expected, but I'm just wondering why it was shown OK when it was just created and eventually disappeared as time goes on.
And how can I use long filename without problem?

@infeo
Copy link
Member

infeo commented Dec 14, 2021

Depends on cryptomator/cryptofs#121 and an update of cryptofs

@infeo infeo added this to the 1.6.5 milestone Dec 14, 2021
@infeo infeo self-assigned this Dec 14, 2021
@infeo infeo closed this as completed in 36f87b3 Dec 16, 2021
@infeo
Copy link
Member

infeo commented Dec 16, 2021

For users affected by this issue: Update to 1.6.5, run the Vault Health Check tool and fix all warnings with the description "org.cryptomator.health.shortend.TrailingBytesInNameFile...".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
misc:filesystem state:confirmed We are able to reproduce the reported behavior type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants