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

Caching is not working properly #312

Closed
Nodens- opened this issue May 26, 2017 · 2 comments
Closed

Caching is not working properly #312

Nodens- opened this issue May 26, 2017 · 2 comments
Labels

Comments

@Nodens-
Copy link

Nodens- commented May 26, 2017

Specifically while a file is still in cache and uploading, any file read operations are not pointing to the cache but to what looks like a 0 byte stub file.
This breaks functionality of every backup software that is trying to perform any kind of "file written" verification after it finishes writing.
Disabling async upload is a workaround that works but
a) It slows the filesystem to a crawl
b) Does not help when there's additional caching or asynchronous transfers from elsewhere (eg samba aio).

Please see here for complete information on my investigation and perhaps you can shed some more light on what is going on: rfjakob/gocryptfs#112

@astrada astrada added the bug label Aug 9, 2017
@astrada
Copy link
Owner

astrada commented Aug 9, 2017

Should be fixed in version 0.6.21 (beta channel).

@Nodens-
Copy link
Author

Nodens- commented Aug 22, 2017

Confirmed. Behavior on 0.6.21 looks normal now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants