C drive used as intermediate before writing data to remote location

I have a problem with Cryptomator that seems to be unintended from what I’ve gathered here.

My C: drive gets filled up when using Cryptomator on a large dataset. From another topic it seems that Cryptomator should write directly to the intended data location but the C drive seems to be used temporarily.

I’ve used task manager to look at what happens while transferring data to my NAS and it seems to buffer in some way, transferring the data to the C drive first (heavy usage of drives) and then after it’s complete with a file it then sends it over the network to the NAS. While there’s heavy usage of my data drive and the C drive there is not network activity so it definitely does not operate directly on the NAS storage.

VeraCrypt can put data directly on remote storage like a NAS without using the C drive where as Cryptomator seems to use the C drive as temporary storage until it then gets send onto the final storage device like a NAS.

Can anyone clarify this? If it’s intended I hope it could be changed in the future as Cryptomator currently is unusable in scenarios with a dataset larger than the C drive.

1 Like

I had the same problem. I have my Cryptomator vaults on D drive. When I copy a file which is on D drive to vault, it first copies it into C drive (negligible CPU usage), then copy into d drive while encrypting (high CPU usage). I have verified it from Task Manager.

I solved it by changing Preferences > Virtual Drive > Volume Type to Fuse. It was WebDAV by default. After switching, I’m not getting any writes to other drive.

When Volume Type is WebDAV, the filesystem used is FAT which limited copying file of size > 4GB. After switching to Fuse, I am able to copy large files.

PS: When copying a file to vault, there is first a lot of write activity (almost the same as file size) without any reads. After that read of the file starts and there is also write activity which is actual writing of file. I’m not sure what’s the purpose of that initial write. I would like to avoid that if possible for the longevity of my SSDs.

© 2022 Skymatic GmbH • Privacy PolicyImpressum